Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05162deecc6cba9452ecc2b78f42e910bb3a23bad5d7769949385dfd7bcbc519

Tx prefix hash: ee2d9befd83bfb2f5fd48a719ac6bfda2fb0a522f1f8866d3240db9a17b8a3e2
Tx public key: e8c4984caef32ed951e8bf067e737ef9bf603c5cb0e3bb2239fdbc7a9e9a9470
Timestamp: 1706464601 Timestamp [UCT]: 2024-01-28 17:56:41 Age [y:d:h:m:s]: 01:141:23:16:03
Block: 945316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362477 RingCT/type: yes/0
Extra: 01e8c4984caef32ed951e8bf067e737ef9bf603c5cb0e3bb2239fdbc7a9e9a94700211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a6a183b2cf21dbd6828aab11c2c2980ddf7be9acc921c4d10ea618a336408d5 0.600000000000 1403628 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": 945326, "vin": [ { "gen": { "height": 945316 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a6a183b2cf21dbd6828aab11c2c2980ddf7be9acc921c4d10ea618a336408d5" } } ], "extra": [ 1, 232, 196, 152, 76, 174, 243, 46, 217, 81, 232, 191, 6, 126, 115, 126, 249, 191, 96, 60, 92, 176, 227, 187, 34, 57, 253, 188, 122, 158, 154, 148, 112, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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