Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac5d7aa1fa9b2aacb149ab1044fed60c59ce10b140d9aba8d866f1546e95663d

Tx prefix hash: 4d5b49604adf8e76c8d05d1344e8ce85bbbe583c5d30cbd2fa6b3c88ec4334d1
Tx public key: a3f3012cacddb4fb5c85947e33010aa505ff5c158e769f8dcaecb19d65833c55
Timestamp: 1762883503 Timestamp [UCT]: 2025-11-11 17:51:43 Age [y:d:h:m:s]: 00:009:19:26:43
Block: 1409959 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7006 RingCT/type: yes/0
Extra: 01a3f3012cacddb4fb5c85947e33010aa505ff5c158e769f8dcaecb19d65833c55021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f939e6d7196ff07ef3e7bab3f03583cf9bcd495f1cf0bb3ce85dc6f186cd42bb 0.600000000000 1898408 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": 1409969, "vin": [ { "gen": { "height": 1409959 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f939e6d7196ff07ef3e7bab3f03583cf9bcd495f1cf0bb3ce85dc6f186cd42bb" } } ], "extra": [ 1, 163, 243, 1, 44, 172, 221, 180, 251, 92, 133, 148, 126, 51, 1, 10, 165, 5, 255, 92, 21, 142, 118, 159, 141, 202, 236, 177, 157, 101, 131, 60, 85, 2, 17, 0, 0, 0, 1, 228, 220, 144, 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