Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 044df5698d92985e6f3aece0b41c06c6d033663df0fc50e1aa225c66105bf9fd

Tx prefix hash: c63eed121fbcd39db32259d771631d6f0f4dc1f13a4b2845d448c3dbaa406e43
Tx public key: e8de373629315faf5c2fa67bef1743098eec96948c1dac01927114e9ce5235d2
Timestamp: 1737561971 Timestamp [UCT]: 2025-01-22 16:06:11 Age [y:d:h:m:s]: 00:148:04:30:32
Block: 1202957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105635 RingCT/type: yes/0
Extra: 01e8de373629315faf5c2fa67bef1743098eec96948c1dac01927114e9ce5235d2021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c52ad703edde8cb1e2ba95c4fd9cf42db0a65bbcdaf307d8446c20b6eaa2116 0.600000000000 1689624 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": 1202967, "vin": [ { "gen": { "height": 1202957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c52ad703edde8cb1e2ba95c4fd9cf42db0a65bbcdaf307d8446c20b6eaa2116" } } ], "extra": [ 1, 232, 222, 55, 54, 41, 49, 95, 175, 92, 47, 166, 123, 239, 23, 67, 9, 142, 236, 150, 148, 140, 29, 172, 1, 146, 113, 20, 233, 206, 82, 53, 210, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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