Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c48af42b1c7bf229f43994ecc939b562c2ccfd0a58138c2df764c9316ad05a65

Tx prefix hash: 2d34ae4c5d42e6beb35625f1ccab8866c9a9329d981155f9a0be08e6e57183c6
Tx public key: 9cc8ce866acc0b48d10263cb8c881bece584d72adceeb47e560a9e0307c6ea17
Timestamp: 1736334263 Timestamp [UCT]: 2025-01-08 11:04:23 Age [y:d:h:m:s]: 00:116:16:15:54
Block: 1192832 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83188 RingCT/type: yes/0
Extra: 019cc8ce866acc0b48d10263cb8c881bece584d72adceeb47e560a9e0307c6ea170211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 872788fb3962be5c0c9a79408565eb7f054db9a87110911730261ce2d93819d0 0.600000000000 1679389 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": 1192842, "vin": [ { "gen": { "height": 1192832 } } ], "vout": [ { "amount": 600000000, "target": { "key": "872788fb3962be5c0c9a79408565eb7f054db9a87110911730261ce2d93819d0" } } ], "extra": [ 1, 156, 200, 206, 134, 106, 204, 11, 72, 209, 2, 99, 203, 140, 136, 27, 236, 229, 132, 215, 42, 220, 238, 180, 126, 86, 10, 158, 3, 7, 198, 234, 23, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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