Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ef2ea078b0d005b9ff745c2f62079e4c6efdec63afe124ab6991f0518a66c88

Tx prefix hash: fc7986e89f01b2c84ff46fe1258fde83905e389136904b56a1e804139d678391
Tx public key: 056c37811a3c161a2a97f9c7d3b1fbffcd19a5fca2effe18e7de940cbe52fe63
Timestamp: 1745729567 Timestamp [UCT]: 2025-04-27 04:52:47 Age [y:d:h:m:s]: 00:010:14:37:05
Block: 1270349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7593 RingCT/type: yes/0
Extra: 01056c37811a3c161a2a97f9c7d3b1fbffcd19a5fca2effe18e7de940cbe52fe630211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9664ad091ae871ab8361a8b27b4064e09213d3cbabefd13af2fc5f044a0edd5a 0.600000000000 1757592 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": 1270359, "vin": [ { "gen": { "height": 1270349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9664ad091ae871ab8361a8b27b4064e09213d3cbabefd13af2fc5f044a0edd5a" } } ], "extra": [ 1, 5, 108, 55, 129, 26, 60, 22, 26, 42, 151, 249, 199, 211, 177, 251, 255, 205, 25, 165, 252, 162, 239, 254, 24, 231, 222, 148, 12, 190, 82, 254, 99, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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