Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41b896e66eb8b88a40df18480b652912e5d6c09910cbbab553ff013ac3f503f9

Tx prefix hash: b796e91975ab45bb8bcfdef47e46d29d6dac6180c96a4969fb0c95a4ae9167cb
Tx public key: 0b71633c3861662895e34a85f6ac4213af1ae4d5bf881b1c1d54a4d85437e64f
Timestamp: 1582097437 Timestamp [UCT]: 2020-02-19 07:30:37 Age [y:d:h:m:s]: 05:065:09:57:32
Block: 67881 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1199977 RingCT/type: yes/0
Extra: 010b71633c3861662895e34a85f6ac4213af1ae4d5bf881b1c1d54a4d85437e64f021100000001c71d3ff9000000000000000000

1 output(s) for total of 365.686983566000 dcy

stealth address amount amount idx
00: 4cb443571374e8b0c35df281296612bfe2e3fba5c6f6adb833564f58b74788b7 365.686983566000 125075 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": 67891, "vin": [ { "gen": { "height": 67881 } } ], "vout": [ { "amount": 365686983566, "target": { "key": "4cb443571374e8b0c35df281296612bfe2e3fba5c6f6adb833564f58b74788b7" } } ], "extra": [ 1, 11, 113, 99, 60, 56, 97, 102, 40, 149, 227, 74, 133, 246, 172, 66, 19, 175, 26, 228, 213, 191, 136, 27, 28, 29, 84, 164, 216, 84, 55, 230, 79, 2, 17, 0, 0, 0, 1, 199, 29, 63, 249, 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