Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4dc14cd6d43a1128cd61ad744cf88d620f9eea3166ae7262da1918aa7e0ef3a0

Tx prefix hash: e782eea8bda2606012c12ccc8f3442b5456d5ddf4017fd796af37981f04ff12b
Tx public key: d7d893bb4617121adff01f4711aafc507e7f33f9a4a128c520d6a5e50b5793b7
Timestamp: 1721542648 Timestamp [UCT]: 2024-07-21 06:17:28 Age [y:d:h:m:s]: 00:271:05:18:09
Block: 1070332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193785 RingCT/type: yes/0
Extra: 01d7d893bb4617121adff01f4711aafc507e7f33f9a4a128c520d6a5e50b5793b7021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65c9d3ac60eed8b8f0507936e3c7fe25d331d75672250c9cf28c414581d0ae4b 0.600000000000 1542123 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": 1070342, "vin": [ { "gen": { "height": 1070332 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65c9d3ac60eed8b8f0507936e3c7fe25d331d75672250c9cf28c414581d0ae4b" } } ], "extra": [ 1, 215, 216, 147, 187, 70, 23, 18, 26, 223, 240, 31, 71, 17, 170, 252, 80, 126, 127, 51, 249, 164, 161, 40, 197, 32, 214, 165, 229, 11, 87, 147, 183, 2, 17, 0, 0, 0, 5, 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