Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4df7c1ab225353a2355e456e6df8de1abdab058cbcb657b332d2fd293cc06ab4

Tx prefix hash: 42661e8124144cb6c3c44e3f5521fdb8cefd55eefc70dae3eea65d5a14b7ca4c
Tx public key: cc09c370149bba2429c5b357db45929eb34033ff9f4049ebd6aa10ef2356a36b
Timestamp: 1747306274 Timestamp [UCT]: 2025-05-15 10:51:14 Age [y:d:h:m:s]: 00:190:06:58:59
Block: 1283411 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133694 RingCT/type: yes/0
Extra: 01cc09c370149bba2429c5b357db45929eb34033ff9f4049ebd6aa10ef2356a36b0211000000029f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fd2bf1f8927b4d0b3ba00911b5cd706b0438b91fc8f9ba4f6c9c7aed081f156 0.600000000000 1770830 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": 1283421, "vin": [ { "gen": { "height": 1283411 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fd2bf1f8927b4d0b3ba00911b5cd706b0438b91fc8f9ba4f6c9c7aed081f156" } } ], "extra": [ 1, 204, 9, 195, 112, 20, 155, 186, 36, 41, 197, 179, 87, 219, 69, 146, 158, 179, 64, 51, 255, 159, 64, 73, 235, 214, 170, 16, 239, 35, 86, 163, 107, 2, 17, 0, 0, 0, 2, 159, 159, 230, 140, 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