Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc87c5fc4a11f99931c72304894d39c2f03982da550875c528d8bd9caf36de42

Tx prefix hash: f88cd939ccffca853271fbab121b267aa649d79cb54f3b54c9590e71fb914e86
Tx public key: 524ddbf70fd1902e6a0fec26899d9082a9e6b110a1e91d11079f81ef41f5a43c
Timestamp: 1713236747 Timestamp [UCT]: 2024-04-16 03:05:47 Age [y:d:h:m:s]: 00:222:10:28:39
Block: 1001476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159240 RingCT/type: yes/0
Extra: 01524ddbf70fd1902e6a0fec26899d9082a9e6b110a1e91d11079f81ef41f5a43c02110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94ec6b8871daf956c478e8d5184038b2c91e4de532c0603a836ae7cb2d5db96e 0.600000000000 1461980 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": 1001486, "vin": [ { "gen": { "height": 1001476 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94ec6b8871daf956c478e8d5184038b2c91e4de532c0603a836ae7cb2d5db96e" } } ], "extra": [ 1, 82, 77, 219, 247, 15, 209, 144, 46, 106, 15, 236, 38, 137, 157, 144, 130, 169, 230, 177, 16, 161, 233, 29, 17, 7, 159, 129, 239, 65, 245, 164, 60, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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