Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 905f26f31d1c5003303221b42e7ff9b0e18fc91b58c40cbf2461809676a7ef2e

Tx prefix hash: 2f3b601b48feee74c6340a3d076372142e348d78d208dfe1dc30667c86d7fd96
Tx public key: 8e54921757dfcecad63df07347a4aef3e193f5e315082ce5cf8e9a15a97fd75f
Timestamp: 1750160331 Timestamp [UCT]: 2025-06-17 11:38:51 Age [y:d:h:m:s]: 00:155:14:36:33
Block: 1306933 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109004 RingCT/type: yes/0
Extra: 018e54921757dfcecad63df07347a4aef3e193f5e315082ce5cf8e9a15a97fd75f02110000000301491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d8e5d16d18055d95c8e53e7dfc263828c45ba30b4100e74b8ac62057a131a8b 0.600000000000 1794542 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": 1306943, "vin": [ { "gen": { "height": 1306933 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d8e5d16d18055d95c8e53e7dfc263828c45ba30b4100e74b8ac62057a131a8b" } } ], "extra": [ 1, 142, 84, 146, 23, 87, 223, 206, 202, 214, 61, 240, 115, 71, 164, 174, 243, 225, 147, 245, 227, 21, 8, 44, 229, 207, 142, 154, 21, 169, 127, 215, 95, 2, 17, 0, 0, 0, 3, 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