Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ec86be7edfc5856de38dfe6f9b9e8a52bd1cc0ced78d61117d2e823eab6f9f7

Tx prefix hash: c97659053c75806c55adf15b5932c95fe90243222ce91617a83fb0c5de2a11d2
Tx public key: a5472e89495205b9241dd1d62b41b93df097b6716f239d4ae825677ff4f0ad5f
Timestamp: 1718049719 Timestamp [UCT]: 2024-06-10 20:01:59 Age [y:d:h:m:s]: 00:254:16:59:47
Block: 1041391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181973 RingCT/type: yes/0
Extra: 01a5472e89495205b9241dd1d62b41b93df097b6716f239d4ae825677ff4f0ad5f0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7fa80216d96ef75cf61745166806b0d83d189ca3fb09b668e5e58e4261c344f 0.600000000000 1510056 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": 1041401, "vin": [ { "gen": { "height": 1041391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7fa80216d96ef75cf61745166806b0d83d189ca3fb09b668e5e58e4261c344f" } } ], "extra": [ 1, 165, 71, 46, 137, 73, 82, 5, 185, 36, 29, 209, 214, 43, 65, 185, 61, 240, 151, 182, 113, 111, 35, 157, 74, 232, 37, 103, 127, 244, 240, 173, 95, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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