Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d9799035b85b2fd124d4e69711ff5224878224e8a2ba3cf1cbf1be145f0525d

Tx prefix hash: 567633d4124fa02a9455ead9be0f3d0f6fe1618bacf21ae71d7bf1c709a2b074
Tx public key: b5c15082be26badc1b1407ca0ea13da4cd620a6c7f0ef5ed542bb137a28ce092
Timestamp: 1723151030 Timestamp [UCT]: 2024-08-08 21:03:50 Age [y:d:h:m:s]: 00:140:01:00:25
Block: 1083673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100189 RingCT/type: yes/0
Extra: 01b5c15082be26badc1b1407ca0ea13da4cd620a6c7f0ef5ed542bb137a28ce092021100000007e914dd15000000000000000000

1 output(s) for total of 0.615590000000 dcy

stealth address amount amount idx
00: ba82f4eb3909a9055af2549fa1c0de933a51493228a1f9cc0d8c12a7481f5105 0.615590000000 1557676 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": 1083683, "vin": [ { "gen": { "height": 1083673 } } ], "vout": [ { "amount": 615590000, "target": { "key": "ba82f4eb3909a9055af2549fa1c0de933a51493228a1f9cc0d8c12a7481f5105" } } ], "extra": [ 1, 181, 193, 80, 130, 190, 38, 186, 220, 27, 20, 7, 202, 14, 161, 61, 164, 205, 98, 10, 108, 127, 14, 245, 237, 84, 43, 177, 55, 162, 140, 224, 146, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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