Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd0fffb8a3c1b7cfccf9957e716e426ad42e5d4a3d2d3af444ef41b7968c0d3f

Tx prefix hash: e3dfdc617235657be8b1ee30eb174dbfc0f6dc2f6fbcd2e3a488fa8db8fba2c6
Tx public key: 6d60f7d002ce71f3cfd982a54eb4717cef46ebb5dc51dbc6f5b7d96df2d1c1ab
Timestamp: 1704713435 Timestamp [UCT]: 2024-01-08 11:30:35 Age [y:d:h:m:s]: 00:327:22:40:09
Block: 930804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234833 RingCT/type: yes/0
Extra: 016d60f7d002ce71f3cfd982a54eb4717cef46ebb5dc51dbc6f5b7d96df2d1c1ab0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 737766eea929b387b5f8308566b834b63a4635fc429ca51b4c4cc22fe408ed55 0.600000000000 1388694 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": 930814, "vin": [ { "gen": { "height": 930804 } } ], "vout": [ { "amount": 600000000, "target": { "key": "737766eea929b387b5f8308566b834b63a4635fc429ca51b4c4cc22fe408ed55" } } ], "extra": [ 1, 109, 96, 247, 208, 2, 206, 113, 243, 207, 217, 130, 165, 78, 180, 113, 124, 239, 70, 235, 181, 220, 81, 219, 198, 245, 183, 217, 109, 242, 209, 193, 171, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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