Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2d0c5732bb65a54508f6d8d4f02372f6d20f12b147428f2ae78926eccbf80d0

Tx prefix hash: 056bba79bc8630b2aa3612820ecfaecd0309522c0fa94d2a8f9a561dda5f3137
Tx public key: 0d55c30dfb733c698d2dcff517b31344f81843faab7b2090c332ccd0941c607c
Timestamp: 1738123877 Timestamp [UCT]: 2025-01-29 04:11:17 Age [y:d:h:m:s]: 00:295:17:39:01
Block: 1207404 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209108 RingCT/type: yes/0
Extra: 010d55c30dfb733c698d2dcff517b31344f81843faab7b2090c332ccd0941c607c0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7acbf45102ae6ac2947a7ceebf2911dc5e59b8edfcacf02ae89b9e08622848e1 0.600000000000 1694127 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": 1207414, "vin": [ { "gen": { "height": 1207404 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7acbf45102ae6ac2947a7ceebf2911dc5e59b8edfcacf02ae89b9e08622848e1" } } ], "extra": [ 1, 13, 85, 195, 13, 251, 115, 60, 105, 141, 45, 207, 245, 23, 179, 19, 68, 248, 24, 67, 250, 171, 123, 32, 144, 195, 50, 204, 208, 148, 28, 96, 124, 2, 17, 0, 0, 0, 1, 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