Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 991a77654ad6e04138202a0148d8c1a64864f8b2fcc8ff4be296761b631859dd

Tx prefix hash: 241f34f46867bcd58819d6356f1ca89a2c9e4164b2075cf5f38eb09f292cac44
Tx public key: 2a81d8171d847eb11fd0ae94928e87617f91d671f361a17a4966419053cb9a2a
Timestamp: 1723392370 Timestamp [UCT]: 2024-08-11 16:06:10 Age [y:d:h:m:s]: 01:091:08:37:40
Block: 1085680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323766 RingCT/type: yes/0
Extra: 012a81d8171d847eb11fd0ae94928e87617f91d671f361a17a4966419053cb9a2a021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d60fb303eb420f58f02afe89b3971bde5b075d81dfb1d5db88342f210e21754 0.600000000000 1560269 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": 1085690, "vin": [ { "gen": { "height": 1085680 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d60fb303eb420f58f02afe89b3971bde5b075d81dfb1d5db88342f210e21754" } } ], "extra": [ 1, 42, 129, 216, 23, 29, 132, 126, 177, 31, 208, 174, 148, 146, 142, 135, 97, 127, 145, 214, 113, 243, 97, 161, 122, 73, 102, 65, 144, 83, 203, 154, 42, 2, 17, 0, 0, 0, 1, 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