Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 333b42364c78b62dca28ad53b24c261107db530da4e001aab6442e1ded8ec19b

Tx prefix hash: 44bd7851b04b4290260441bc25424623777dfd64f8e5cf0dbbc3ec946331eccd
Tx public key: 16eb833b099f84818b08b6ac5b54e1147467d5e69dac1cf1bab4e2e5aee99017
Timestamp: 1699351714 Timestamp [UCT]: 2023-11-07 10:08:34 Age [y:d:h:m:s]: 02:002:19:28:58
Block: 886372 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 521788 RingCT/type: yes/0
Extra: 0116eb833b099f84818b08b6ac5b54e1147467d5e69dac1cf1bab4e2e5aee9901702110000000233af99f4000000000000000000

1 output(s) for total of 0.709711131000 dcy

stealth address amount amount idx
00: ae5bcd3f52c71bc38a0755cd02bdf3ae3e99541fa31f9daa99821b4ddc1cc27d 0.709711131000 1342187 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": 886382, "vin": [ { "gen": { "height": 886372 } } ], "vout": [ { "amount": 709711131, "target": { "key": "ae5bcd3f52c71bc38a0755cd02bdf3ae3e99541fa31f9daa99821b4ddc1cc27d" } } ], "extra": [ 1, 22, 235, 131, 59, 9, 159, 132, 129, 139, 8, 182, 172, 91, 84, 225, 20, 116, 103, 213, 230, 157, 172, 28, 241, 186, 180, 226, 229, 174, 233, 144, 23, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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