Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a279d2764f59ed58048d2bbc6c193cc8b99e38e55681d21ca728dbf2c6960d23

Tx prefix hash: 420cae4bd282f2a761078db6f8dcc488cde617a887d9f2e6c734b102fc7c9b56
Tx public key: 1d404d5653591817e5ca3f10924ae08ffc590bc0a4b2bf793d81b6b1c4107105
Timestamp: 1717426435 Timestamp [UCT]: 2024-06-03 14:53:55 Age [y:d:h:m:s]: 00:346:09:41:20
Block: 1036232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247580 RingCT/type: yes/0
Extra: 011d404d5653591817e5ca3f10924ae08ffc590bc0a4b2bf793d81b6b1c41071050211000000020cce0636000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1abc5a75923a35fcdbae08605cbafd1cee20e56717a7f913c1b62f2484a68462 0.600000000000 1504757 of 15

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": 1036242, "vin": [ { "gen": { "height": 1036232 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1abc5a75923a35fcdbae08605cbafd1cee20e56717a7f913c1b62f2484a68462" } } ], "extra": [ 1, 29, 64, 77, 86, 83, 89, 24, 23, 229, 202, 63, 16, 146, 74, 224, 143, 252, 89, 11, 192, 164, 178, 191, 121, 61, 129, 182, 177, 196, 16, 113, 5, 2, 17, 0, 0, 0, 2, 12, 206, 6, 54, 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