Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5aae6586005a549bdd2d04e4d24cd7741778b3a6d75a76428d6a5d1c808f031

Tx prefix hash: 34ae8e5d1b36a69f6fddfc3aed07e1f14221df6e96542cab6df9aa223324226f
Tx public key: 50d652165ff89ec13d9e622c662d0803cce80bf930985741c7209e015669e4df
Timestamp: 1687789873 Timestamp [UCT]: 2023-06-26 14:31:13 Age [y:d:h:m:s]: 02:148:04:30:54
Block: 790780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 625652 RingCT/type: yes/0
Extra: 0150d652165ff89ec13d9e622c662d0803cce80bf930985741c7209e015669e4df02110000000233af99f4000000000000000000

1 output(s) for total of 1.471694731000 dcy

stealth address amount amount idx
00: a4e476b9e845fde88072e3750fdc6ccc189a0ae57817fbd6ac16ce913ada9f97 1.471694731000 1241201 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": 790790, "vin": [ { "gen": { "height": 790780 } } ], "vout": [ { "amount": 1471694731, "target": { "key": "a4e476b9e845fde88072e3750fdc6ccc189a0ae57817fbd6ac16ce913ada9f97" } } ], "extra": [ 1, 80, 214, 82, 22, 95, 248, 158, 193, 61, 158, 98, 44, 102, 45, 8, 3, 204, 232, 11, 249, 48, 152, 87, 65, 199, 32, 158, 1, 86, 105, 228, 223, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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