Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff91c412cf7bdbd127878db11ec23a702fbb6e5f580be2121f7ee6245751b9d9

Tx prefix hash: 010d0da7e675681c16e6156451e01fa8ec84c8b4cfe09809c5f807519bb7056a
Tx public key: 205c2065a20044768d307a73ecfe161547def413f2df97c7533c4b4ae7b67de5
Timestamp: 1723550652 Timestamp [UCT]: 2024-08-13 12:04:12 Age [y:d:h:m:s]: 00:231:15:05:55
Block: 1086995 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165411 RingCT/type: yes/0
Extra: 01205c2065a20044768d307a73ecfe161547def413f2df97c7533c4b4ae7b67de502110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed3db7b9a97e89cf1e8a1b3c7b47d28cc9c69bbaea63550e249073d5d7796a89 0.600000000000 1561596 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": 1087005, "vin": [ { "gen": { "height": 1086995 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed3db7b9a97e89cf1e8a1b3c7b47d28cc9c69bbaea63550e249073d5d7796a89" } } ], "extra": [ 1, 32, 92, 32, 101, 162, 0, 68, 118, 141, 48, 122, 115, 236, 254, 22, 21, 71, 222, 244, 19, 242, 223, 151, 199, 83, 60, 75, 74, 231, 182, 125, 229, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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