Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5f8662f2c62789296a84597629c1d93fe3fc303d7ab8ffcc72f4a5cb3d493bc

Tx prefix hash: bb9247ccabc68c44c87e6fc14ef0929d88b520203caa35b3bdbf908d8d701b42
Tx public key: bcaa5ad4ebdd84fe48835c72abcf48c9d6018f206eda79d3dab96c3b0f5a7756
Timestamp: 1763216381 Timestamp [UCT]: 2025-11-15 14:19:41 Age [y:d:h:m:s]: 00:075:19:28:25
Block: 1412709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54108 RingCT/type: yes/0
Extra: 01bcaa5ad4ebdd84fe48835c72abcf48c9d6018f206eda79d3dab96c3b0f5a77560211000000028ceb7f09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f06637b3964d5e4c0fcb505a71a1e4cb0a03d08cf218dc4af80f747a1ac5be6 0.600000000000 1901180 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": 1412719, "vin": [ { "gen": { "height": 1412709 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f06637b3964d5e4c0fcb505a71a1e4cb0a03d08cf218dc4af80f747a1ac5be6" } } ], "extra": [ 1, 188, 170, 90, 212, 235, 221, 132, 254, 72, 131, 92, 114, 171, 207, 72, 201, 214, 1, 143, 32, 110, 218, 121, 211, 218, 185, 108, 59, 15, 90, 119, 86, 2, 17, 0, 0, 0, 2, 140, 235, 127, 9, 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