Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ac23154f31bab9c3907cdeb6b5727b823beb0e3e6525d32b39b56638725ecf0

Tx prefix hash: 502c66f8c2363cfde0b3d56ef05146e59986efecfb9d9b93a41f04f7845d3d07
Tx public key: 60a6270bc33d49f4891a547567f88ada694190f362b03c899ef9f8da2c34d41f
Timestamp: 1751329852 Timestamp [UCT]: 2025-07-01 00:30:52 Age [y:d:h:m:s]: 00:142:21:15:49
Block: 1316204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100307 RingCT/type: yes/0
Extra: 0160a6270bc33d49f4891a547567f88ada694190f362b03c899ef9f8da2c34d41f021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d0a2b77389dee660a4e27c32c16c677a36f84c29060f0a9dc0ba045316b0e9b 0.600000000000 1803861 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": 1316214, "vin": [ { "gen": { "height": 1316204 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d0a2b77389dee660a4e27c32c16c677a36f84c29060f0a9dc0ba045316b0e9b" } } ], "extra": [ 1, 96, 166, 39, 11, 195, 61, 73, 244, 137, 26, 84, 117, 103, 248, 138, 218, 105, 65, 144, 243, 98, 176, 60, 137, 158, 249, 248, 218, 44, 52, 212, 31, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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