Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe113b1794b34c1d0e6f1fbca432e0e4ae50fe9c544e94f08e264a301dc60eb0

Tx prefix hash: 49c7cd57f03ad8e8a9202eb00b9076820a4f1f1608361fcaf380b52b5191659b
Tx public key: 92c857f3a43424b67cf1140bc8c4aa90cdb3556a3a84b0183c6d62da480b12f3
Timestamp: 1705593865 Timestamp [UCT]: 2024-01-18 16:04:25 Age [y:d:h:m:s]: 01:322:00:49:22
Block: 938103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 488998 RingCT/type: yes/0
Extra: 0192c857f3a43424b67cf1140bc8c4aa90cdb3556a3a84b0183c6d62da480b12f302110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1f063f014885fef5a8196748baeb451153259efafe5ab275087a3030b0b64dc 0.600000000000 1396169 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": 938113, "vin": [ { "gen": { "height": 938103 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1f063f014885fef5a8196748baeb451153259efafe5ab275087a3030b0b64dc" } } ], "extra": [ 1, 146, 200, 87, 243, 164, 52, 36, 182, 124, 241, 20, 11, 200, 196, 170, 144, 205, 179, 85, 106, 58, 132, 176, 24, 60, 109, 98, 218, 72, 11, 18, 243, 2, 17, 0, 0, 0, 10, 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