Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e62e05bd7459e7722bfb8d676c99bf03fe1a1e39bcc973c8515cde04dd2133e

Tx prefix hash: 0f5db3beaf92475f8d2b2f281d23345553850389840b0b613a8b70af61eba026
Tx public key: 6e3b0b8ed0dd3dc752542f0ac38f7ac5ac790227d6ec5bedb4f7de0c61abb501
Timestamp: 1685794467 Timestamp [UCT]: 2023-06-03 12:14:27 Age [y:d:h:m:s]: 01:270:06:47:55
Block: 774222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 454335 RingCT/type: yes/0
Extra: 016e3b0b8ed0dd3dc752542f0ac38f7ac5ac790227d6ec5bedb4f7de0c61abb50102110000000575e3f0e9000000000000000000

1 output(s) for total of 1.669864711000 dcy

stealth address amount amount idx
00: c37f2f679c4d3b79e11d72939e16e6bef77b3e502fa82fb5bdafedb6a3c48102 1.669864711000 1223691 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": 774232, "vin": [ { "gen": { "height": 774222 } } ], "vout": [ { "amount": 1669864711, "target": { "key": "c37f2f679c4d3b79e11d72939e16e6bef77b3e502fa82fb5bdafedb6a3c48102" } } ], "extra": [ 1, 110, 59, 11, 142, 208, 221, 61, 199, 82, 84, 47, 10, 195, 143, 122, 197, 172, 121, 2, 39, 214, 236, 91, 237, 180, 247, 222, 12, 97, 171, 181, 1, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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