Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2f3280bb0ed539f790928b7554fb73733cf61819866aab2b29b2b1541dae8c2

Tx prefix hash: 4600f9d8b5b5b9b9f128f4c452da77bd12cc64f5e9a2150e3ca55776ef44cbac
Tx public key: 7406869457fc141c2e10b8f43a07474bf85fbfd3d816a2a915faf48b55e98ff8
Timestamp: 1762593572 Timestamp [UCT]: 2025-11-08 09:19:32 Age [y:d:h:m:s]: 00:058:10:58:19
Block: 1407554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41873 RingCT/type: yes/0
Extra: 017406869457fc141c2e10b8f43a07474bf85fbfd3d816a2a915faf48b55e98ff8021100000004df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: caa8dd55f27cbb25e1eb923848960a946cc18e9ef4dc4622c38cd6c81a096e9c 0.600000000000 1895975 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": 1407564, "vin": [ { "gen": { "height": 1407554 } } ], "vout": [ { "amount": 600000000, "target": { "key": "caa8dd55f27cbb25e1eb923848960a946cc18e9ef4dc4622c38cd6c81a096e9c" } } ], "extra": [ 1, 116, 6, 134, 148, 87, 252, 20, 28, 46, 16, 184, 244, 58, 7, 71, 75, 248, 95, 191, 211, 216, 22, 162, 169, 21, 250, 244, 139, 85, 233, 143, 248, 2, 17, 0, 0, 0, 4, 223, 90, 36, 122, 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