Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08c5d66dfb5f30dc307a85505f30b09db224d84aca433ad4839c97112eded623

Tx prefix hash: dc5667e12ed574a0dc9383fd50737e933cb80fbafe1df9dc952c3eec8c63b056
Tx public key: 1bbc3025a1279ad7e1558a2b19ef49d1483c2cb8d8bc7b7387bdc31425848682
Timestamp: 1751750445 Timestamp [UCT]: 2025-07-05 21:20:45 Age [y:d:h:m:s]: 00:208:22:29:53
Block: 1319505 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147608 RingCT/type: yes/0
Extra: 011bbc3025a1279ad7e1558a2b19ef49d1483c2cb8d8bc7b7387bdc3142584868202110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be4b91e6adcc3ee29a62c8ca908ed265b562046f3a5ecfb9cfa4d600fefefca7 0.600000000000 1807198 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": 1319515, "vin": [ { "gen": { "height": 1319505 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be4b91e6adcc3ee29a62c8ca908ed265b562046f3a5ecfb9cfa4d600fefefca7" } } ], "extra": [ 1, 27, 188, 48, 37, 161, 39, 154, 215, 225, 85, 138, 43, 25, 239, 73, 209, 72, 60, 44, 184, 216, 188, 123, 115, 135, 189, 195, 20, 37, 132, 134, 130, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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