Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5296b6926e0b9b4248d3194bb7517358c3a7081ca98468080835cff0368359f4

Tx prefix hash: c9bfc2b99b038aa09b34c054f8f1c41577ae4cee61eec71a2b21e8074043b2c8
Tx public key: 4c92e927b89a925f83e586dc2d2f0cba1365a0aa77208cd95450197a8e93875e
Timestamp: 1682511880 Timestamp [UCT]: 2023-04-26 12:24:40 Age [y:d:h:m:s]: 01:357:22:01:25
Block: 747006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 517074 RingCT/type: yes/0
Extra: 014c92e927b89a925f83e586dc2d2f0cba1365a0aa77208cd95450197a8e93875e021100000001b3164c24000000000000000000

1 output(s) for total of 2.055224330000 dcy

stealth address amount amount idx
00: f7f9894b15a756cbcc4c2e8fbcbc5abc4aa898817f51d0e7d5ddf9105d2f8157 2.055224330000 1194631 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": 747016, "vin": [ { "gen": { "height": 747006 } } ], "vout": [ { "amount": 2055224330, "target": { "key": "f7f9894b15a756cbcc4c2e8fbcbc5abc4aa898817f51d0e7d5ddf9105d2f8157" } } ], "extra": [ 1, 76, 146, 233, 39, 184, 154, 146, 95, 131, 229, 134, 220, 45, 47, 12, 186, 19, 101, 160, 170, 119, 32, 140, 217, 84, 80, 25, 122, 142, 147, 135, 94, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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