Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: de48c6e3698c006d9f44a6deb36ecf209d5068f58c8e02926c93b4507381616b

Tx prefix hash: a2d8a9587dee9eeb16a65095f57c8f0bcfa0a32d07f4296a896c047cc0455879
Tx public key: 869f4a92845eaad8eb35152c6a2f89c82f6b5cc61b0168f2075bf1784968720a
Timestamp: 1681925248 Timestamp [UCT]: 2023-04-19 17:27:28 Age [y:d:h:m:s]: 01:310:13:10:49
Block: 742141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 483175 RingCT/type: yes/0
Extra: 01869f4a92845eaad8eb35152c6a2f89c82f6b5cc61b0168f2075bf1784968720a021100000004e6d27f9c000000000000000000

1 output(s) for total of 2.132941795000 dcy

stealth address amount amount idx
00: c4558b765f89cbae0d124ff428f1fec450398e9e492fd5bee5ac67f71ac374b1 2.132941795000 1189098 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 742151, "vin": [ { "gen": { "height": 742141 } } ], "vout": [ { "amount": 2132941795, "target": { "key": "c4558b765f89cbae0d124ff428f1fec450398e9e492fd5bee5ac67f71ac374b1" } } ], "extra": [ 1, 134, 159, 74, 146, 132, 94, 170, 216, 235, 53, 21, 44, 106, 47, 137, 200, 47, 107, 92, 198, 27, 1, 104, 242, 7, 91, 241, 120, 73, 104, 114, 10, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8