Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b84030579b7c55388cfa25c7f933bfac0a044f7d8a08b75ea982c9adfebcbedd

Tx prefix hash: 1dc523b375e76f65a4bfd59a7f2c8ea82e40389e95685abd2910484ff1c6b065
Tx public key: d5f650217bf8e114abec17e3462cd5144c9923bf97ebfc274d3d2c016a08edcd
Timestamp: 1716207246 Timestamp [UCT]: 2024-05-20 12:14:06 Age [y:d:h:m:s]: 00:187:19:46:43
Block: 1026109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134442 RingCT/type: yes/0
Extra: 01d5f650217bf8e114abec17e3462cd5144c9923bf97ebfc274d3d2c016a08edcd021100000004e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1963c2fa1b35aa6acc5f4abda803c44492f5efc0bc88234ddef4a0b296696eb3 0.600000000000 1493018 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": 1026119, "vin": [ { "gen": { "height": 1026109 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1963c2fa1b35aa6acc5f4abda803c44492f5efc0bc88234ddef4a0b296696eb3" } } ], "extra": [ 1, 213, 246, 80, 33, 123, 248, 225, 20, 171, 236, 23, 227, 70, 44, 213, 20, 76, 153, 35, 191, 151, 235, 252, 39, 77, 61, 44, 1, 106, 8, 237, 205, 2, 17, 0, 0, 0, 4, 224, 133, 50, 182, 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