Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 057c655fbb2f589190d689ec0ac1c17708200bdc23e01c14d752167cd298e11c

Tx prefix hash: d95e5e48069b3abf8b5653b435bf01c98e020a1a28f8147faf5f85b7aad5d950
Tx public key: 5b51033d77859ac5897c7f69449a41eaa98fba74d869e184aadd7029d93af2b5
Timestamp: 1705144761 Timestamp [UCT]: 2024-01-13 11:19:21 Age [y:d:h:m:s]: 01:047:08:59:04
Block: 934381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294933 RingCT/type: yes/0
Extra: 015b51033d77859ac5897c7f69449a41eaa98fba74d869e184aadd7029d93af2b502110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c3c74044b1e2f2f664bb5806c23414d684f6b6c0cd3f090ca6a702b80b329a6 0.600000000000 1392389 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": 934391, "vin": [ { "gen": { "height": 934381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c3c74044b1e2f2f664bb5806c23414d684f6b6c0cd3f090ca6a702b80b329a6" } } ], "extra": [ 1, 91, 81, 3, 61, 119, 133, 154, 197, 137, 124, 127, 105, 68, 154, 65, 234, 169, 143, 186, 116, 216, 105, 225, 132, 170, 221, 112, 41, 217, 58, 242, 181, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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