Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fffdd76ebc314701baddc0b6787ef4b8623ce25d33c31dd67840dc9a1766171f

Tx prefix hash: d0b8deceda13a8f4731bbf2448bc17d26bf19cdd8dfe7c02a5ca83b947506e60
Tx public key: f07afb9b30f043c55adde8ecdc5197f909636c5f5dbb84f697bf13fbd67a2be0
Timestamp: 1711540454 Timestamp [UCT]: 2024-03-27 11:54:14 Age [y:d:h:m:s]: 00:230:22:45:33
Block: 987452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165306 RingCT/type: yes/0
Extra: 01f07afb9b30f043c55adde8ecdc5197f909636c5f5dbb84f697bf13fbd67a2be00211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bcd9834c405ab4d3300a226e423c35fd8c64e20224c869e69c1fe7d1b0f03157 0.600000000000 1447701 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": 987462, "vin": [ { "gen": { "height": 987452 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcd9834c405ab4d3300a226e423c35fd8c64e20224c869e69c1fe7d1b0f03157" } } ], "extra": [ 1, 240, 122, 251, 155, 48, 240, 67, 197, 90, 221, 232, 236, 220, 81, 151, 249, 9, 99, 108, 95, 93, 187, 132, 246, 151, 191, 19, 251, 214, 122, 43, 224, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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