Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24e4bb476773878c7be1b2d90cb0a3bae6640d27829c3f659fca451c503c5d0f

Tx prefix hash: 3f8717c0d7ddbe3f48a0aa9572d914ad0bd9ee130834bbe833ee2951bdc930aa
Tx public key: 1ec3ec3d1bca7d80ed72d159431f47d6cf050c2f27568821e3e1d8a2ec307266
Timestamp: 1696821513 Timestamp [UCT]: 2023-10-09 03:18:33 Age [y:d:h:m:s]: 01:188:19:07:08
Block: 865599 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395966 RingCT/type: yes/0
Extra: 011ec3ec3d1bca7d80ed72d159431f47d6cf050c2f27568821e3e1d8a2ec30726602110000000775e3f0e9000000000000000000

1 output(s) for total of 0.831593756000 dcy

stealth address amount amount idx
00: 4efc8c654d64db7ea5775d676ddfaa7c0477d74ad59369d4006d0a3c5a610697 0.831593756000 1320137 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": 865609, "vin": [ { "gen": { "height": 865599 } } ], "vout": [ { "amount": 831593756, "target": { "key": "4efc8c654d64db7ea5775d676ddfaa7c0477d74ad59369d4006d0a3c5a610697" } } ], "extra": [ 1, 30, 195, 236, 61, 27, 202, 125, 128, 237, 114, 209, 89, 67, 31, 71, 214, 207, 5, 12, 47, 39, 86, 136, 33, 227, 225, 216, 162, 236, 48, 114, 102, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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