Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a5abb72a93ca92ff68e8d2ad368ec140d1b1acfb4d65c851ebfe38ade1def0d

Tx prefix hash: bb09b663e540508eca960c75d32e102565b953189c7be8f3260c7c63ffaeb15a
Tx public key: 03f79f5433578a0d0802517d79448402996aa1449fde5cb816f0110490d21f6b
Timestamp: 1750878147 Timestamp [UCT]: 2025-06-25 19:02:27 Age [y:d:h:m:s]: 00:141:12:37:16
Block: 1312683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99126 RingCT/type: yes/0
Extra: 0103f79f5433578a0d0802517d79448402996aa1449fde5cb816f0110490d21f6b021100000005bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1ea4842950a14e1c6e0d0ab69aef6a36774a68dfb17a64c2325d8a29d057c5f 0.600000000000 1800318 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": 1312693, "vin": [ { "gen": { "height": 1312683 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1ea4842950a14e1c6e0d0ab69aef6a36774a68dfb17a64c2325d8a29d057c5f" } } ], "extra": [ 1, 3, 247, 159, 84, 51, 87, 138, 13, 8, 2, 81, 125, 121, 68, 132, 2, 153, 106, 161, 68, 159, 222, 92, 184, 22, 240, 17, 4, 144, 210, 31, 107, 2, 17, 0, 0, 0, 5, 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