Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 080c7867312dfd61c8530169ec62525387066be1797fab4134f5d7c450276441

Tx prefix hash: d48eac06e94bfc3a46c6e5ce3ebcc8dc6bd874e8c757cba4eb4e3fb0147682db
Tx public key: 017e7a204875880abe4a0bcbbe85a25148d0ae240c5cf62d3967c17d7b3d1a8f
Timestamp: 1733426241 Timestamp [UCT]: 2024-12-05 19:17:21 Age [y:d:h:m:s]: 00:110:19:44:16
Block: 1168780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78961 RingCT/type: yes/0
Extra: 01017e7a204875880abe4a0bcbbe85a25148d0ae240c5cf62d3967c17d7b3d1a8f021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a0283657c6eb1f88178005352a2d23caa544600df4a93266715164d77cebfc3 0.600000000000 1654491 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": 1168790, "vin": [ { "gen": { "height": 1168780 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a0283657c6eb1f88178005352a2d23caa544600df4a93266715164d77cebfc3" } } ], "extra": [ 1, 1, 126, 122, 32, 72, 117, 136, 10, 190, 74, 11, 203, 190, 133, 162, 81, 72, 208, 174, 36, 12, 92, 246, 45, 57, 103, 193, 125, 123, 61, 26, 143, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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