Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77b2c1cba12cb6ca410416081343209b76cdc13a6caa6fcfe47b8174aeb621e1

Tx prefix hash: be5d37efa3a326ca235ddf012ec2181fe2722f570a7ec137da620429c2a53a15
Tx public key: fcdf505902bd35cd35992f8e8642bc271ed381ea068877cda3d2b90b5e2ba8e5
Timestamp: 1677279350 Timestamp [UCT]: 2023-02-24 22:55:50 Age [y:d:h:m:s]: 02:114:02:17:15
Block: 704264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 603054 RingCT/type: yes/0
Extra: 01fcdf505902bd35cd35992f8e8642bc271ed381ea068877cda3d2b90b5e2ba8e50211000000075029cbac000000000000000000

1 output(s) for total of 2.847612700000 dcy

stealth address amount amount idx
00: 0b470e8666f20a2cf7afdcba28786334dc22e1377dd9a5e57cb06d392f403a0f 2.847612700000 1147925 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": 704274, "vin": [ { "gen": { "height": 704264 } } ], "vout": [ { "amount": 2847612700, "target": { "key": "0b470e8666f20a2cf7afdcba28786334dc22e1377dd9a5e57cb06d392f403a0f" } } ], "extra": [ 1, 252, 223, 80, 89, 2, 189, 53, 205, 53, 153, 47, 142, 134, 66, 188, 39, 30, 211, 129, 234, 6, 136, 119, 205, 163, 210, 185, 11, 94, 43, 168, 229, 2, 17, 0, 0, 0, 7, 80, 41, 203, 172, 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