Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7a85fa7662a09cbb002ebae43b4b733015e8c11874b4c3248eb7ded737e9be2

Tx prefix hash: e4583dea501f9b547a002a2f796a23b8d68d3167fa2afe0730be99e15b2e718b
Tx public key: 62f8b5e2051ef84c17fb518fe84584d119cbb17db54f3c21acf7baffe8ceb37d
Timestamp: 1675585493 Timestamp [UCT]: 2023-02-05 08:24:53 Age [y:d:h:m:s]: 02:061:07:13:07
Block: 690214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 565423 RingCT/type: yes/0
Extra: 0162f8b5e2051ef84c17fb518fe84584d119cbb17db54f3c21acf7baffe8ceb37d0211000000025029cbac000000000000000000

1 output(s) for total of 3.169818707000 dcy

stealth address amount amount idx
00: 63c26424fbbe759259075f4e8d0e7ba1d9217ebe42d2672354a80f8d77b443a4 3.169818707000 1132934 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": 690224, "vin": [ { "gen": { "height": 690214 } } ], "vout": [ { "amount": 3169818707, "target": { "key": "63c26424fbbe759259075f4e8d0e7ba1d9217ebe42d2672354a80f8d77b443a4" } } ], "extra": [ 1, 98, 248, 181, 226, 5, 30, 248, 76, 23, 251, 81, 143, 232, 69, 132, 209, 25, 203, 177, 125, 181, 79, 60, 33, 172, 247, 186, 255, 232, 206, 179, 125, 2, 17, 0, 0, 0, 2, 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