Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99e22b45677c3229926340ad4f81ca2bbf6b9e96277351fc21733db82690d608

Tx prefix hash: 241c233128728651a317966bad5d6a3fabebbaa1821a120364d41c180b468f46
Tx public key: d74c01e2852f4886e1c45d7b2fe582c69daa90fa0b5edfb838d37de63b61ae69
Timestamp: 1578665765 Timestamp [UCT]: 2020-01-10 14:16:05 Age [y:d:h:m:s]: 05:140:12:32:00
Block: 42764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1250424 RingCT/type: yes/0
Extra: 01d74c01e2852f4886e1c45d7b2fe582c69daa90fa0b5edfb838d37de63b61ae690211000000114ac5aa02000000000000000000

1 output(s) for total of 442.990924649000 dcy

stealth address amount amount idx
00: b6a410c9ade3ceddd3e763b2d529676a9bc77f66b6e5ff360dda38cc7d646706 442.990924649000 77129 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": 42774, "vin": [ { "gen": { "height": 42764 } } ], "vout": [ { "amount": 442990924649, "target": { "key": "b6a410c9ade3ceddd3e763b2d529676a9bc77f66b6e5ff360dda38cc7d646706" } } ], "extra": [ 1, 215, 76, 1, 226, 133, 47, 72, 134, 225, 196, 93, 123, 47, 229, 130, 198, 157, 170, 144, 250, 11, 94, 223, 184, 56, 211, 125, 230, 59, 97, 174, 105, 2, 17, 0, 0, 0, 17, 74, 197, 170, 2, 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