Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 695b595a2a217a713c73c2b316f4a64d7a06ca407448c99180b0c12cf48348a4

Tx prefix hash: cd471018ce04bf0f42bcfbcdb27ffe11337a75d24002cc6d80966a78b791f73d
Tx public key: f97872a9c77118f668fa06f9921f0c1d8a5f408d7e5085a23cbda8b9ab18a137
Timestamp: 1713737702 Timestamp [UCT]: 2024-04-21 22:15:02 Age [y:d:h:m:s]: 00:262:06:55:20
Block: 1005628 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187747 RingCT/type: yes/0
Extra: 01f97872a9c77118f668fa06f9921f0c1d8a5f408d7e5085a23cbda8b9ab18a1370211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17c1d5e685570d72095ce50923874a166918d24fcbe6351cdce819eef18006c0 0.600000000000 1466378 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": 1005638, "vin": [ { "gen": { "height": 1005628 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17c1d5e685570d72095ce50923874a166918d24fcbe6351cdce819eef18006c0" } } ], "extra": [ 1, 249, 120, 114, 169, 199, 113, 24, 246, 104, 250, 6, 249, 146, 31, 12, 29, 138, 95, 64, 141, 126, 80, 133, 162, 60, 189, 168, 185, 171, 24, 161, 55, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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