Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c711c4d9a0e835f697ad4bee1d27ca8cf33a2ed4ee79f0f02d8809900be9be7f

Tx prefix hash: d33b5d2018b92d6f5c4d9719133956433479f24a5fec19bed06bfeb8e6bfb450
Tx public key: 2047d066840be3528e99a6425a84005e8429d218dfd7cca94389ccc975e3bf91
Timestamp: 1721821531 Timestamp [UCT]: 2024-07-24 11:45:31 Age [y:d:h:m:s]: 00:267:00:34:36
Block: 1072648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190768 RingCT/type: yes/0
Extra: 012047d066840be3528e99a6425a84005e8429d218dfd7cca94389ccc975e3bf91021100000020e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef5d2f2c572f37ad49e3e49c686992b5ff6c80d2b49956bbeee5fd4aedca2c62 0.600000000000 1545133 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": 1072658, "vin": [ { "gen": { "height": 1072648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef5d2f2c572f37ad49e3e49c686992b5ff6c80d2b49956bbeee5fd4aedca2c62" } } ], "extra": [ 1, 32, 71, 208, 102, 132, 11, 227, 82, 142, 153, 166, 66, 90, 132, 0, 94, 132, 41, 210, 24, 223, 215, 204, 169, 67, 137, 204, 201, 117, 227, 191, 145, 2, 17, 0, 0, 0, 32, 233, 20, 221, 21, 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