Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67d6ad4857d4b3b43ddbebd10994e1eb8dd92428f5a9e4ed1cc0202b79fc61e9

Tx prefix hash: e6a296e84a5d6ac95174df5b47c803b7977ea65cb9348bb92ec9227f74168e35
Tx public key: 1f6731b6304e2b4accc3c7e1f3c7d697388657e11e96cfff57c26c3037e2013d
Timestamp: 1706596477 Timestamp [UCT]: 2024-01-30 06:34:37 Age [y:d:h:m:s]: 01:281:15:50:05
Block: 946408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 460097 RingCT/type: yes/0
Extra: 011f6731b6304e2b4accc3c7e1f3c7d697388657e11e96cfff57c26c3037e2013d0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44a2eaffb4757caa5aff4ef9bc7c1dcda9d4785240ae12a641f557855b7cf135 0.600000000000 1404740 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": 946418, "vin": [ { "gen": { "height": 946408 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44a2eaffb4757caa5aff4ef9bc7c1dcda9d4785240ae12a641f557855b7cf135" } } ], "extra": [ 1, 31, 103, 49, 182, 48, 78, 43, 74, 204, 195, 199, 225, 243, 199, 214, 151, 56, 134, 87, 225, 30, 150, 207, 255, 87, 194, 108, 48, 55, 226, 1, 61, 2, 17, 0, 0, 0, 2, 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