Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b02b9240a37ee30dfb9bbbf0001f0e49666ee298bbe67cee0b7e25738c085167

Tx prefix hash: 943f94e3a2cad1438942838cdccb04d6035b0b993fc0c9d5a75bc0a54f85cc5f
Tx public key: 7e3672fb845a9a7373a4fc82f1b5e595539e1d23908bf076e8108df90b3aca91
Timestamp: 1707711981 Timestamp [UCT]: 2024-02-12 04:26:21 Age [y:d:h:m:s]: 00:347:18:50:33
Block: 955670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248930 RingCT/type: yes/0
Extra: 017e3672fb845a9a7373a4fc82f1b5e595539e1d23908bf076e8108df90b3aca910211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 803e51973b5f4d3935b9dde3cda0951675a13595cf31dd1bc557236931cb3d76 0.600000000000 1414968 of 15

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": 955680, "vin": [ { "gen": { "height": 955670 } } ], "vout": [ { "amount": 600000000, "target": { "key": "803e51973b5f4d3935b9dde3cda0951675a13595cf31dd1bc557236931cb3d76" } } ], "extra": [ 1, 126, 54, 114, 251, 132, 90, 154, 115, 115, 164, 252, 130, 241, 181, 229, 149, 83, 158, 29, 35, 144, 139, 240, 118, 232, 16, 141, 249, 11, 58, 202, 145, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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