Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17bf6ba3eaad61136b8274cf4b16dda21ae76c3af808527844d288e94c08c4cf

Tx prefix hash: 760eb7ef8c4c170cd4bf40feb953cf837a65312ae4554ab0bf263d96168b8f7c
Tx public key: 388be778153944df033ccb6b0aad0b5a4a15f1cdecc35a3db17a1603316919a5
Timestamp: 1583849403 Timestamp [UCT]: 2020-03-10 14:10:03 Age [y:d:h:m:s]: 04:193:21:35:19
Block: 79674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1033805 RingCT/type: yes/0
Extra: 01388be778153944df033ccb6b0aad0b5a4a15f1cdecc35a3db17a1603316919a502110000000128db8c57000000000000000000

1 output(s) for total of 334.201007013000 dcy

stealth address amount amount idx
00: cb16271794e93a9abc2dc4921cd30f66a2cf2f20d16a980ccba6b194dd7c30a4 334.201007013000 145822 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": 79684, "vin": [ { "gen": { "height": 79674 } } ], "vout": [ { "amount": 334201007013, "target": { "key": "cb16271794e93a9abc2dc4921cd30f66a2cf2f20d16a980ccba6b194dd7c30a4" } } ], "extra": [ 1, 56, 139, 231, 120, 21, 57, 68, 223, 3, 60, 203, 107, 10, 173, 11, 90, 74, 21, 241, 205, 236, 195, 90, 61, 177, 122, 22, 3, 49, 105, 25, 165, 2, 17, 0, 0, 0, 1, 40, 219, 140, 87, 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