Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec68c851e78d075707baca9ecfaba489591e761f96e6e6bcd0da2c3490b02c49

Tx prefix hash: b6f8710cabd17cd7be8b809792356875593f81c4397507d19da6c833922960f5
Tx public key: a8d395e4b0e8bab16c4c1bdf6230ba767cc264f2440200c9ddbcf7a3a582d0d6
Timestamp: 1577728939 Timestamp [UCT]: 2019-12-30 18:02:19 Age [y:d:h:m:s]: 05:004:00:03:05
Block: 35216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1152816 RingCT/type: yes/0
Extra: 01a8d395e4b0e8bab16c4c1bdf6230ba767cc264f2440200c9ddbcf7a3a582d0d60211000000068a2ee0d9000000000000000000

1 output(s) for total of 469.154220720000 dcy

stealth address amount amount idx
00: e39ab7be8b995daf8992ea918ec7e61140f9379bdac2a1411988d7138e9b7020 469.154220720000 59306 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": 35226, "vin": [ { "gen": { "height": 35216 } } ], "vout": [ { "amount": 469154220720, "target": { "key": "e39ab7be8b995daf8992ea918ec7e61140f9379bdac2a1411988d7138e9b7020" } } ], "extra": [ 1, 168, 211, 149, 228, 176, 232, 186, 177, 108, 76, 27, 223, 98, 48, 186, 118, 124, 194, 100, 242, 68, 2, 0, 201, 221, 188, 247, 163, 165, 130, 208, 214, 2, 17, 0, 0, 0, 6, 138, 46, 224, 217, 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