Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74333a4fbcf64401b9b71c923e447ef4396f74742abb39a5d370be2463c9aa14

Tx prefix hash: 65cbd57cad216abbb6aafe9896e42386d4e17010b109c457ec8d1eb3ad90a5e3
Tx public key: 961f9725c4e2344d68325f46178a9c1655b49a0c89e77fe9a737a2b221af75d0
Timestamp: 1635611026 Timestamp [UCT]: 2021-10-30 16:23:46 Age [y:d:h:m:s]: 03:026:05:12:10
Block: 363745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 797211 RingCT/type: yes/0
Extra: 01961f9725c4e2344d68325f46178a9c1655b49a0c89e77fe9a737a2b221af75d002110000000c4f792ffd000000000000000000

1 output(s) for total of 38.261520145000 dcy

stealth address amount amount idx
00: 38e07e82d1d04672e82a280f0071ab4d4fc9176220d5fe771bcfd985934e6c1f 38.261520145000 739183 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": 363755, "vin": [ { "gen": { "height": 363745 } } ], "vout": [ { "amount": 38261520145, "target": { "key": "38e07e82d1d04672e82a280f0071ab4d4fc9176220d5fe771bcfd985934e6c1f" } } ], "extra": [ 1, 150, 31, 151, 37, 196, 226, 52, 77, 104, 50, 95, 70, 23, 138, 156, 22, 85, 180, 154, 12, 137, 231, 127, 233, 167, 55, 162, 178, 33, 175, 117, 208, 2, 17, 0, 0, 0, 12, 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