Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff67408e4d682949d517cc9ee98683fd880b9d8bbeb89dc18205da9cd242e96e

Tx prefix hash: 4c0d91a5c61bab232bfdd9d63c47b233529b10486aeab44a697862520fae9a91
Tx public key: 0156cd237fca5fad065a906ffae06fb52a112c6a2c670d2d75c68852f05772b0
Timestamp: 1699542607 Timestamp [UCT]: 2023-11-09 15:10:07 Age [y:d:h:m:s]: 01:140:13:52:19
Block: 887961 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361648 RingCT/type: yes/0
Extra: 010156cd237fca5fad065a906ffae06fb52a112c6a2c670d2d75c68852f05772b00211000000024b8f5122000000000000000000

1 output(s) for total of 0.701159137000 dcy

stealth address amount amount idx
00: 6226e2f01d80919e531fa7b42ae68c0bd27a4a56a1a2b09911be6cebc2966292 0.701159137000 1343874 of 0

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": 887971, "vin": [ { "gen": { "height": 887961 } } ], "vout": [ { "amount": 701159137, "target": { "key": "6226e2f01d80919e531fa7b42ae68c0bd27a4a56a1a2b09911be6cebc2966292" } } ], "extra": [ 1, 1, 86, 205, 35, 127, 202, 95, 173, 6, 90, 144, 111, 250, 224, 111, 181, 42, 17, 44, 106, 44, 103, 13, 45, 117, 198, 136, 82, 240, 87, 114, 176, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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