Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bf66d66a2331783a3a98fe30ff1379cd1a56b24d3413543297020a2af056b69

Tx prefix hash: 674cf29fd1bea3c1828a0df569ff50f08a991eaf231dd8e1a91835c9dffa2ab7
Tx public key: d3c53b5c709f02464905b36ff0cf35e6b6f5dfea0ac9f7a349143427d83c5c78
Timestamp: 1754631486 Timestamp [UCT]: 2025-08-08 05:38:06 Age [y:d:h:m:s]: 00:112:00:14:49
Block: 1342614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79158 RingCT/type: yes/0
Extra: 01d3c53b5c709f02464905b36ff0cf35e6b6f5dfea0ac9f7a349143427d83c5c7802110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e5005e098adb01c53e9601851ecf4c1549b16005bbf3cc35b0dd95416aaabc1 0.600000000000 1830447 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": 1342624, "vin": [ { "gen": { "height": 1342614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e5005e098adb01c53e9601851ecf4c1549b16005bbf3cc35b0dd95416aaabc1" } } ], "extra": [ 1, 211, 197, 59, 92, 112, 159, 2, 70, 73, 5, 179, 111, 240, 207, 53, 230, 182, 245, 223, 234, 10, 201, 247, 163, 73, 20, 52, 39, 216, 60, 92, 120, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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