Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c609f33b87f475e5bcc12d698c200daa06eeffad1e2f405b60c17c3126d9777d

Tx prefix hash: 744a7fd5207b007a474fea2eb96f480da447a8fb920dfe2155e3f53d70699a21
Tx public key: 6f6a9e6b242ae63e6fc63c68d57ba0c2ebc1dc066039b6ee3d42cb2e1e9a726e
Timestamp: 1714880604 Timestamp [UCT]: 2024-05-05 03:43:24 Age [y:d:h:m:s]: 01:020:16:41:26
Block: 1015131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275723 RingCT/type: yes/0
Extra: 016f6a9e6b242ae63e6fc63c68d57ba0c2ebc1dc066039b6ee3d42cb2e1e9a726e0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8c8ee93659a1f827232c7763ddfda9e8b3aca74c561e712eb159c12cd2dfce0 0.600000000000 1478406 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": 1015141, "vin": [ { "gen": { "height": 1015131 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8c8ee93659a1f827232c7763ddfda9e8b3aca74c561e712eb159c12cd2dfce0" } } ], "extra": [ 1, 111, 106, 158, 107, 36, 42, 230, 62, 111, 198, 60, 104, 213, 123, 160, 194, 235, 193, 220, 6, 96, 57, 182, 238, 61, 66, 203, 46, 30, 154, 114, 110, 2, 17, 0, 0, 0, 2, 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