Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f06e05d3afb53e7583e1a6c23810543f9ef9289e4e65fad27829b7c164ea2494

Tx prefix hash: b0844b267be0bca768a68762f2f28d101d848113ee7a1a7cba8702d223af801a
Tx public key: 7c0429df6f70eff94d71c80c86d023015b71e2e1903e9dd511329baa08af25b5
Timestamp: 1738008220 Timestamp [UCT]: 2025-01-27 20:03:40 Age [y:d:h:m:s]: 00:140:10:10:17
Block: 1206456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100306 RingCT/type: yes/0
Extra: 017c0429df6f70eff94d71c80c86d023015b71e2e1903e9dd511329baa08af25b502110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 134e126514aad36806f0702f4d036f6d1e34c17cb8fdc1bf8542504e9742faf3 0.600000000000 1693161 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": 1206466, "vin": [ { "gen": { "height": 1206456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "134e126514aad36806f0702f4d036f6d1e34c17cb8fdc1bf8542504e9742faf3" } } ], "extra": [ 1, 124, 4, 41, 223, 111, 112, 239, 249, 77, 113, 200, 12, 134, 208, 35, 1, 91, 113, 226, 225, 144, 62, 157, 213, 17, 50, 155, 170, 8, 175, 37, 181, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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