Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 996439785037f0a2074aaa7d1afb3027ba956a5f4294a7cac03df509ba366af7

Tx prefix hash: 51a02b13ebdf394ee187dadc9c3f63599d2f5686239393fe6e68d8e6b79f26da
Tx public key: 3e31244bc49865c3e2446baf0d00c729f5fe4a4f8cd6c2f33fb73b3032e27977
Timestamp: 1715493719 Timestamp [UCT]: 2024-05-12 06:01:59 Age [y:d:h:m:s]: 00:243:22:45:25
Block: 1020224 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174570 RingCT/type: yes/0
Extra: 013e31244bc49865c3e2446baf0d00c729f5fe4a4f8cd6c2f33fb73b3032e2797702110000000241ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d6dec84873184763b5e9362bc3ca8c5d46320803a084a42dade76219357aa71 0.600000000000 1484285 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": 1020234, "vin": [ { "gen": { "height": 1020224 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d6dec84873184763b5e9362bc3ca8c5d46320803a084a42dade76219357aa71" } } ], "extra": [ 1, 62, 49, 36, 75, 196, 152, 101, 195, 226, 68, 107, 175, 13, 0, 199, 41, 245, 254, 74, 79, 140, 214, 194, 243, 63, 183, 59, 48, 50, 226, 121, 119, 2, 17, 0, 0, 0, 2, 65, 238, 28, 155, 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