Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6cc15a4344a7c9d6e0ad3b18f0b91948e584cc62a0968bdb0dc3b3cb297e5dd

Tx prefix hash: da7d14d8f2633c6a5d6c77990094affe05eaa06f8ffb408018cbe9dc6bd4e164
Tx public key: 82960b013e732fa10f786e4e52d4980c32aa15fe46661a622746d94d503b321e
Timestamp: 1737757522 Timestamp [UCT]: 2025-01-24 22:25:22 Age [y:d:h:m:s]: 00:332:04:31:47
Block: 1204575 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235010 RingCT/type: yes/0
Extra: 0182960b013e732fa10f786e4e52d4980c32aa15fe46661a622746d94d503b321e021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63d6f10f640bf820368271d53e17d3c7e10cd71418dc1ff14a10cbea9ee09aba 0.600000000000 1691264 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": 1204585, "vin": [ { "gen": { "height": 1204575 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63d6f10f640bf820368271d53e17d3c7e10cd71418dc1ff14a10cbea9ee09aba" } } ], "extra": [ 1, 130, 150, 11, 1, 62, 115, 47, 161, 15, 120, 110, 78, 82, 212, 152, 12, 50, 170, 21, 254, 70, 102, 26, 98, 39, 70, 217, 77, 80, 59, 50, 30, 2, 17, 0, 0, 0, 2, 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