Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5c44da00ee6f965aedd3317229a250a3b210293c99cff009224cdc3bb317185

Tx prefix hash: 993bdd9fce8a4c7c4e9e1aaa9da1367498054752f2913346196fc51bdc310cf5
Tx public key: bacd94e9c0b0ea77643e2e57a0adb97e2178ed3256488f9b83430a11565df9e2
Timestamp: 1694653283 Timestamp [UCT]: 2023-09-14 01:01:23 Age [y:d:h:m:s]: 01:209:20:01:06
Block: 847596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411069 RingCT/type: yes/0
Extra: 01bacd94e9c0b0ea77643e2e57a0adb97e2178ed3256488f9b83430a11565df9e20211000000084b8f5122000000000000000000

1 output(s) for total of 0.954031377000 dcy

stealth address amount amount idx
00: 356b45360109a64017fb124bce1907f2e5d7c186c6ddf4e62df4625ed5c9cf0d 0.954031377000 1301132 of 0

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": 847606, "vin": [ { "gen": { "height": 847596 } } ], "vout": [ { "amount": 954031377, "target": { "key": "356b45360109a64017fb124bce1907f2e5d7c186c6ddf4e62df4625ed5c9cf0d" } } ], "extra": [ 1, 186, 205, 148, 233, 192, 176, 234, 119, 100, 62, 46, 87, 160, 173, 185, 126, 33, 120, 237, 50, 86, 72, 143, 155, 131, 67, 10, 17, 86, 93, 249, 226, 2, 17, 0, 0, 0, 8, 75, 143, 81, 34, 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