Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc657fad66856d0761afedb83f3b31cab7bbfa4c6ad416200436f94a58e22ff3

Tx prefix hash: bf698f6ff1ecc5cd299ae4e49ffb2adcc947c1bf9b26f46bb580cb4574d352cf
Tx public key: 514309e2784d367c1974a0f4eebb94396d79e1e88c1918f1db99c05196e75240
Timestamp: 1751594452 Timestamp [UCT]: 2025-07-04 02:00:52 Age [y:d:h:m:s]: 00:133:23:02:04
Block: 1318317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94003 RingCT/type: yes/0
Extra: 01514309e2784d367c1974a0f4eebb94396d79e1e88c1918f1db99c05196e7524002110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d4b1ffb9a8c49f3887846a55a79afef1c2d037444a5b946a7527711e79b93df 0.600000000000 1805996 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": 1318327, "vin": [ { "gen": { "height": 1318317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d4b1ffb9a8c49f3887846a55a79afef1c2d037444a5b946a7527711e79b93df" } } ], "extra": [ 1, 81, 67, 9, 226, 120, 77, 54, 124, 25, 116, 160, 244, 238, 187, 148, 57, 109, 121, 225, 232, 140, 25, 24, 241, 219, 153, 192, 81, 150, 231, 82, 64, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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