Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ebd48a0c173ae8d4c168959e6a605c19d38566a9acee9460374d32ff9aee2df

Tx prefix hash: 444696df8dc81e399de2bae8ae3431398795aef60c9cf1233cc43891c64eb1b2
Tx public key: c2265d6a4ae2b567f6cac3f0944ea48e4677be8f15d30ec91ee2e9263c8495b5
Timestamp: 1580118849 Timestamp [UCT]: 2020-01-27 09:54:09 Age [y:d:h:m:s]: 04:340:23:00:10
Block: 53916 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1133846 RingCT/type: yes/0
Extra: 01c2265d6a4ae2b567f6cac3f0944ea48e4677be8f15d30ec91ee2e9263c8495b502110000000149b77a3d000000000000000000

1 output(s) for total of 406.775453236000 dcy

stealth address amount amount idx
00: cb7321e7e11a9769c7b874b6e885890ca78d33ceb540b6c4f9dcb903286e98f9 406.775453236000 99891 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": 53926, "vin": [ { "gen": { "height": 53916 } } ], "vout": [ { "amount": 406775453236, "target": { "key": "cb7321e7e11a9769c7b874b6e885890ca78d33ceb540b6c4f9dcb903286e98f9" } } ], "extra": [ 1, 194, 38, 93, 106, 74, 226, 181, 103, 246, 202, 195, 240, 148, 78, 164, 142, 70, 119, 190, 143, 21, 211, 14, 201, 30, 226, 233, 38, 60, 132, 149, 181, 2, 17, 0, 0, 0, 1, 73, 183, 122, 61, 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