Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c8de481da73698a2b9b3f2eb4ec0555f19ce41b804d85eb2e957cd96c800f21

Tx prefix hash: a36784a8c53e5bda8a030547fffade616442203d077964bbd9aa340b39c5eacc
Tx public key: d71f19d549b72c57db1ab9b5f516a7ddebb0cac204c12cc8eac8cedbd7c0df3a
Timestamp: 1728378082 Timestamp [UCT]: 2024-10-08 09:01:22 Age [y:d:h:m:s]: 00:177:04:20:13
Block: 1127016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126420 RingCT/type: yes/0
Extra: 01d71f19d549b72c57db1ab9b5f516a7ddebb0cac204c12cc8eac8cedbd7c0df3a021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4cdbab0f4d8fccd2bf47ab1c2de58a71a7ead159158722410935ca6f256d7e05 0.600000000000 1609815 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": 1127026, "vin": [ { "gen": { "height": 1127016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4cdbab0f4d8fccd2bf47ab1c2de58a71a7ead159158722410935ca6f256d7e05" } } ], "extra": [ 1, 215, 31, 25, 213, 73, 183, 44, 87, 219, 26, 185, 181, 245, 22, 167, 221, 235, 176, 202, 194, 4, 193, 44, 200, 234, 200, 206, 219, 215, 192, 223, 58, 2, 17, 0, 0, 0, 8, 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