Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a03ca818bf817f3ab67737b7be7773a6bab90ba45577bf5e4822f18a9358998

Tx prefix hash: 3b3a5f3e17f424fcedcec5c3677528aec22d063bdd94d0446076a2ac5e4489e3
Tx public key: 6f7ed08039bf66318eeb12e7f431f54d64389f2052cf8fd61b00f1fa48fe982b
Timestamp: 1748520511 Timestamp [UCT]: 2025-05-29 12:08:31 Age [y:d:h:m:s]: 00:175:16:09:33
Block: 1293479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123219 RingCT/type: yes/0
Extra: 016f7ed08039bf66318eeb12e7f431f54d64389f2052cf8fd61b00f1fa48fe982b0211000000026a75b171000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64f4c9cf0b7345659458d0f0e1dd5e47fd09d9203c67c874fb1257c7460e5461 0.600000000000 1780952 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": 1293489, "vin": [ { "gen": { "height": 1293479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64f4c9cf0b7345659458d0f0e1dd5e47fd09d9203c67c874fb1257c7460e5461" } } ], "extra": [ 1, 111, 126, 208, 128, 57, 191, 102, 49, 142, 235, 18, 231, 244, 49, 245, 77, 100, 56, 159, 32, 82, 207, 143, 214, 27, 0, 241, 250, 72, 254, 152, 43, 2, 17, 0, 0, 0, 2, 106, 117, 177, 113, 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