Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e972e2381f7e91709a89255ddc79c1f4267edd86d4102ea2ec3027edf094a16b

Tx prefix hash: 3f1284820701d2d470802d3748bb0f14d4ee68d0c2c1b2200d26891705aae7e0
Tx public key: 01c7a81f4a27b90e26fe00db5ba355d3e9b8f76c55a829cfd286287c786a9675
Timestamp: 1715060757 Timestamp [UCT]: 2024-05-07 05:45:57 Age [y:d:h:m:s]: 01:185:10:36:05
Block: 1016616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391148 RingCT/type: yes/0
Extra: 0101c7a81f4a27b90e26fe00db5ba355d3e9b8f76c55a829cfd286287c786a967502110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bbdd1b96e7c0a4df02f2738f3d222b0a38c65ae0c915b2c8efb2dbc7b4ab4326 0.600000000000 1480247 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": 1016626, "vin": [ { "gen": { "height": 1016616 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bbdd1b96e7c0a4df02f2738f3d222b0a38c65ae0c915b2c8efb2dbc7b4ab4326" } } ], "extra": [ 1, 1, 199, 168, 31, 74, 39, 185, 14, 38, 254, 0, 219, 91, 163, 85, 211, 233, 184, 247, 108, 85, 168, 41, 207, 210, 134, 40, 124, 120, 106, 150, 117, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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