Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34385b2b3c31fb9c23e908b3ab841898c2a337a921d10f6a3d97e1f47490d47c

Tx prefix hash: d567c11f32fd5f035e1a3108c69b42b5c1cf1947f1506b0b80e906a701217238
Tx public key: 7973ea64820d597d4ea86f3293b0f3a7bfe57c162b4ce535cf9968c5c0d87943
Timestamp: 1726834366 Timestamp [UCT]: 2024-09-20 12:12:46 Age [y:d:h:m:s]: 00:247:13:45:01
Block: 1114216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176801 RingCT/type: yes/0
Extra: 017973ea64820d597d4ea86f3293b0f3a7bfe57c162b4ce535cf9968c5c0d8794302110000000170fe4a94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a80dc8cfeb7c55469f0dce6cf5c7684cfed3fb0bbcae4ad7a72ac0239d775b1 0.600000000000 1594015 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": 1114226, "vin": [ { "gen": { "height": 1114216 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a80dc8cfeb7c55469f0dce6cf5c7684cfed3fb0bbcae4ad7a72ac0239d775b1" } } ], "extra": [ 1, 121, 115, 234, 100, 130, 13, 89, 125, 78, 168, 111, 50, 147, 176, 243, 167, 191, 229, 124, 22, 43, 76, 229, 53, 207, 153, 104, 197, 192, 216, 121, 67, 2, 17, 0, 0, 0, 1, 112, 254, 74, 148, 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