Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a9de9c43601f5d852b7983b3c437a018386e2a79c942657489fb41cc97f3976

Tx prefix hash: 7be0abef916c82872bdb290eb91d3e5443ea9ea21528c0dc82e178faa77b6226
Tx public key: 215c72bb5a2a2d52b7382b3986e67beade1ebd89367e4d4ee8cb4732a09321e8
Timestamp: 1753822368 Timestamp [UCT]: 2025-07-29 20:52:48 Age [y:d:h:m:s]: 00:082:08:46:32
Block: 1336184 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57677 RingCT/type: yes/0
Extra: 01215c72bb5a2a2d52b7382b3986e67beade1ebd89367e4d4ee8cb4732a09321e80211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91acb7ffce53c14c525b7be2bcd18fa6a4e327d530a31b75bbef833a4567f209 0.600000000000 1823985 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": 1336194, "vin": [ { "gen": { "height": 1336184 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91acb7ffce53c14c525b7be2bcd18fa6a4e327d530a31b75bbef833a4567f209" } } ], "extra": [ 1, 33, 92, 114, 187, 90, 42, 45, 82, 183, 56, 43, 57, 134, 230, 123, 234, 222, 30, 189, 137, 54, 126, 77, 78, 232, 203, 71, 50, 160, 147, 33, 232, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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