Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4fbbc6a1605ba87b3f1c8d7c63b32e6fd925059b94b9f1cef34fdeb9e2f97b0

Tx prefix hash: 798a4fe40b3a36bf1474fe8e4466957e50c80c57cd4ea7398f9587a1ad4382d5
Tx public key: 288e1c9c628df1e25d4a1624deafcb5af31918909fa0846b48c806ebd36863e1
Timestamp: 1733968970 Timestamp [UCT]: 2024-12-12 02:02:50 Age [y:d:h:m:s]: 00:139:05:55:59
Block: 1173275 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99319 RingCT/type: yes/0
Extra: 01288e1c9c628df1e25d4a1624deafcb5af31918909fa0846b48c806ebd36863e102110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e51378e0587a354f31a183296ef40129c34cd0d0c10e2a53a9f526545d6aff7 0.600000000000 1659280 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": 1173285, "vin": [ { "gen": { "height": 1173275 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e51378e0587a354f31a183296ef40129c34cd0d0c10e2a53a9f526545d6aff7" } } ], "extra": [ 1, 40, 142, 28, 156, 98, 141, 241, 226, 93, 74, 22, 36, 222, 175, 203, 90, 243, 25, 24, 144, 159, 160, 132, 107, 72, 200, 6, 235, 211, 104, 99, 225, 2, 17, 0, 0, 0, 11, 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