Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6d6095d4c4844dba81aa7a541339c0289f3cd77e73023498de3f4ef9abf516a

Tx prefix hash: 10088c3e396a2a9ca38371a6f016d1530c78da566886644bb82f1069b8274bf0
Tx public key: 53c18f2419ae8158c2602cd5c862841ceea07e85c9345fb0ec516737cdc3d1c4
Timestamp: 1709051345 Timestamp [UCT]: 2024-02-27 16:29:05 Age [y:d:h:m:s]: 01:054:14:43:01
Block: 966792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300047 RingCT/type: yes/0
Extra: 0153c18f2419ae8158c2602cd5c862841ceea07e85c9345fb0ec516737cdc3d1c40211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a909cc52a0fe0f529977a66bf1979ab4452f33c8c8ee97b362645cb5fb24b09 0.600000000000 1426563 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": 966802, "vin": [ { "gen": { "height": 966792 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a909cc52a0fe0f529977a66bf1979ab4452f33c8c8ee97b362645cb5fb24b09" } } ], "extra": [ 1, 83, 193, 143, 36, 25, 174, 129, 88, 194, 96, 44, 213, 200, 98, 132, 28, 238, 160, 126, 133, 201, 52, 95, 176, 236, 81, 103, 55, 205, 195, 209, 196, 2, 17, 0, 0, 0, 1, 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