Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af10271cb65560ab89238dc535bffa0da5eedf0e21e3f251cf9bbba3a62b0ca1

Tx prefix hash: 8ec1c2f4328a208da579e9a3f64d02734974e9ca0199a54330477a7104b4bdf9
Tx public key: 74047f3de77a68676be0da918845c6c6e5dc49dbaf24ec4936e64794bf920e36
Timestamp: 1577198210 Timestamp [UCT]: 2019-12-24 14:36:50 Age [y:d:h:m:s]: 05:024:11:55:12
Block: 30787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1167510 RingCT/type: yes/0
Extra: 0174047f3de77a68676be0da918845c6c6e5dc49dbaf24ec4936e64794bf920e360211000000b978873133000000000000000000

1 output(s) for total of 485.278163977000 dcy

stealth address amount amount idx
00: c9c9bcb7afc68ea318bd8f229885412d18b6db8988268d19cb1bd42a9b6cedc0 485.278163977000 50827 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": 30797, "vin": [ { "gen": { "height": 30787 } } ], "vout": [ { "amount": 485278163977, "target": { "key": "c9c9bcb7afc68ea318bd8f229885412d18b6db8988268d19cb1bd42a9b6cedc0" } } ], "extra": [ 1, 116, 4, 127, 61, 231, 122, 104, 103, 107, 224, 218, 145, 136, 69, 198, 198, 229, 220, 73, 219, 175, 36, 236, 73, 54, 230, 71, 148, 191, 146, 14, 54, 2, 17, 0, 0, 0, 185, 120, 135, 49, 51, 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