Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3a7b57784c63c7df712a9cf59ba22a6db29db2d726fd1c38daf759c4bce807f

Tx prefix hash: 911ec8fa554d99c45f909f14133aac1b865b5d5718f003b8f30f64d226155643
Tx public key: f1597b7b2a17909284996ad18d2be7a967fec99d28bcae07aef8b1796bacc3f0
Timestamp: 1745840007 Timestamp [UCT]: 2025-04-28 11:33:27 Age [y:d:h:m:s]: 00:010:02:03:27
Block: 1271270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7211 RingCT/type: yes/0
Extra: 01f1597b7b2a17909284996ad18d2be7a967fec99d28bcae07aef8b1796bacc3f002110000000a9f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0297e30eb27116ab3ebc2b97a9191f46c4f5af2bdca887b8c954e0f56de86677 0.600000000000 1758527 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": 1271280, "vin": [ { "gen": { "height": 1271270 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0297e30eb27116ab3ebc2b97a9191f46c4f5af2bdca887b8c954e0f56de86677" } } ], "extra": [ 1, 241, 89, 123, 123, 42, 23, 144, 146, 132, 153, 106, 209, 141, 43, 231, 169, 103, 254, 201, 157, 40, 188, 174, 7, 174, 248, 177, 121, 107, 172, 195, 240, 2, 17, 0, 0, 0, 10, 159, 159, 230, 140, 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