Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d74cc4dcacaf3f3cb08826f8c2c43ea859ba3c81f562716d550991de6e95b0c1

Tx prefix hash: 2d0d605aa5d484828142d541dd5f7f7e2d4be9618339a163553b20a234996617
Tx public key: 877a51737ab73b06ccb91f64e49ec0a9680cffa01728ee386abe4e3ee3acd054
Timestamp: 1635939776 Timestamp [UCT]: 2021-11-03 11:42:56 Age [y:d:h:m:s]: 03:097:06:22:47
Block: 366444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 847800 RingCT/type: yes/0
Extra: 01877a51737ab73b06ccb91f64e49ec0a9680cffa01728ee386abe4e3ee3acd05402110000000a4f792ffd000000000000000000

1 output(s) for total of 37.481702509000 dcy

stealth address amount amount idx
00: 9b39c45666d8e1f960d12dd846737b5c691a9195c8ea04fcd258fa109e5929b6 37.481702509000 743852 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": 366454, "vin": [ { "gen": { "height": 366444 } } ], "vout": [ { "amount": 37481702509, "target": { "key": "9b39c45666d8e1f960d12dd846737b5c691a9195c8ea04fcd258fa109e5929b6" } } ], "extra": [ 1, 135, 122, 81, 115, 122, 183, 59, 6, 204, 185, 31, 100, 228, 158, 192, 169, 104, 12, 255, 160, 23, 40, 238, 56, 106, 190, 78, 62, 227, 172, 208, 84, 2, 17, 0, 0, 0, 10, 79, 121, 47, 253, 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