Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c89ffbd3d6250b6d42e72a82eaa1f2aff384d48f43ea14e5d5d81edd1d9617d

Tx prefix hash: bb530bdcde3978fad941860a1e57f505312300763442dad8e11ab7884d4f27cb
Tx public key: c37cc982ea1fc3b61f1353562ad411cc97246987e1e5e1e4cd6330f0976da47f
Timestamp: 1733796134 Timestamp [UCT]: 2024-12-10 02:02:14 Age [y:d:h:m:s]: 00:109:09:08:09
Block: 1171837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77960 RingCT/type: yes/0
Extra: 01c37cc982ea1fc3b61f1353562ad411cc97246987e1e5e1e4cd6330f0976da47f0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f28e5795c1b49c2c8094d6caa0f582366f8817418f5693109135cc45b03bc3dd 0.600000000000 1657650 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": 1171847, "vin": [ { "gen": { "height": 1171837 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f28e5795c1b49c2c8094d6caa0f582366f8817418f5693109135cc45b03bc3dd" } } ], "extra": [ 1, 195, 124, 201, 130, 234, 31, 195, 182, 31, 19, 83, 86, 42, 212, 17, 204, 151, 36, 105, 135, 225, 229, 225, 228, 205, 99, 48, 240, 151, 109, 164, 127, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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