Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aabc48b801e5aab4094d833e6b0bb7214adfbcfccc1222dab8c4d4d6616c7566

Tx prefix hash: 608a23661488c2d8b622f4ded7dbe83bc7f79ead6d7e08246e842f917d3468be
Tx public key: b2f8e7baed26a46004f403624adfd08bb6f2fa3c67361786f8900ff571364a78
Timestamp: 1750396662 Timestamp [UCT]: 2025-06-20 05:17:42 Age [y:d:h:m:s]: 00:148:23:13:23
Block: 1308850 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104289 RingCT/type: yes/0
Extra: 01b2f8e7baed26a46004f403624adfd08bb6f2fa3c67361786f8900ff571364a78021100000006bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 606a238ee8e7a39c53d1c15c62248a4d5af5c6fc9ddb0efbb37297b3d1a4832f 0.600000000000 1796465 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": 1308860, "vin": [ { "gen": { "height": 1308850 } } ], "vout": [ { "amount": 600000000, "target": { "key": "606a238ee8e7a39c53d1c15c62248a4d5af5c6fc9ddb0efbb37297b3d1a4832f" } } ], "extra": [ 1, 178, 248, 231, 186, 237, 38, 164, 96, 4, 244, 3, 98, 74, 223, 208, 139, 182, 242, 250, 60, 103, 54, 23, 134, 248, 144, 15, 245, 113, 54, 74, 120, 2, 17, 0, 0, 0, 6, 191, 81, 178, 162, 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