Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff4a7b0ec2fd53d763de7e2b19e328c492b763b074f8f97240f86370e7880cf9

Tx prefix hash: 28adbfd70897998cf040dab8ac6b14be0eed70ed2edc683a0b1b84999edd8e86
Tx public key: 7c68f1319bd94b0e7fcdfd5b343f8eb0f38e8170b667deb957498cb7aee0be2a
Timestamp: 1762041520 Timestamp [UCT]: 2025-11-01 23:58:40 Age [y:d:h:m:s]: 00:004:22:16:54
Block: 1402985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3520 RingCT/type: yes/0
Extra: 017c68f1319bd94b0e7fcdfd5b343f8eb0f38e8170b667deb957498cb7aee0be2a021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0264e4d164b384cb3e4967cc5073cee88ed6d9efea772ded0a125e3959d15634 0.600000000000 1891312 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": 1402995, "vin": [ { "gen": { "height": 1402985 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0264e4d164b384cb3e4967cc5073cee88ed6d9efea772ded0a125e3959d15634" } } ], "extra": [ 1, 124, 104, 241, 49, 155, 217, 75, 14, 127, 205, 253, 91, 52, 63, 142, 176, 243, 142, 129, 112, 182, 103, 222, 185, 87, 73, 140, 183, 174, 224, 190, 42, 2, 17, 0, 0, 0, 2, 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