Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 145d1ac16156b0965a6b0177756009282620a064b85cb38c4dbb08d60a74caad

Tx prefix hash: 632a39bd3d58955b2f3d3df29e3b2235381fa9c157558a8a8f6f76fcc1fbcddc
Tx public key: fbadd5edb03f6648506dc18d56ae33470a14da742bba16a484ef0bfb8b25cbf1
Timestamp: 1734795539 Timestamp [UCT]: 2024-12-21 15:38:59 Age [y:d:h:m:s]: 00:105:07:58:55
Block: 1180134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75034 RingCT/type: yes/0
Extra: 01fbadd5edb03f6648506dc18d56ae33470a14da742bba16a484ef0bfb8b25cbf10211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b94f9a2dc6b50c54a26c69b033be12c1e0eaa5e79fc299f0e2101ce989d8dc94 0.600000000000 1666539 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": 1180144, "vin": [ { "gen": { "height": 1180134 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b94f9a2dc6b50c54a26c69b033be12c1e0eaa5e79fc299f0e2101ce989d8dc94" } } ], "extra": [ 1, 251, 173, 213, 237, 176, 63, 102, 72, 80, 109, 193, 141, 86, 174, 51, 71, 10, 20, 218, 116, 43, 186, 22, 164, 132, 239, 11, 251, 139, 37, 203, 241, 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