Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8966ff782346ca0d758d38cf0775eec66bf3bf75b5bca99c6f59dc630c939e4

Tx prefix hash: ca903418d9523c6b0e5ee891c4ef7fd1ffbef64eb143a93c3ba9b19fe2bb6b80
Tx public key: edb7bcde7e4e70e859ad46d36dd2545591b82a1b2d4a545e9c39f7754f1d2494
Timestamp: 1731634421 Timestamp [UCT]: 2024-11-15 01:33:41 Age [y:d:h:m:s]: 00:189:00:30:21
Block: 1153916 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134962 RingCT/type: yes/0
Extra: 01edb7bcde7e4e70e859ad46d36dd2545591b82a1b2d4a545e9c39f7754f1d24940211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2de698dd718e809d87b739b6080fb6ffef0d2356080f9cc3b411167704e414ea 0.600000000000 1639527 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": 1153926, "vin": [ { "gen": { "height": 1153916 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2de698dd718e809d87b739b6080fb6ffef0d2356080f9cc3b411167704e414ea" } } ], "extra": [ 1, 237, 183, 188, 222, 126, 78, 112, 232, 89, 173, 70, 211, 109, 210, 84, 85, 145, 184, 42, 27, 45, 74, 84, 94, 156, 57, 247, 117, 79, 29, 36, 148, 2, 17, 0, 0, 0, 5, 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