Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c41c55aaedde847d714f405104393eff4a15644acffd7f3e386403cc9f108d32

Tx prefix hash: fefb869b21f04e0b897dccf749c75aad40af127b0e5299eb5110dbc565496a23
Tx public key: 770e470ac4cff424643a98d197f01ca0e291d5380d8f91c9ef672f2171b36a2c
Timestamp: 1583077706 Timestamp [UCT]: 2020-03-01 15:48:26 Age [y:d:h:m:s]: 04:304:03:28:52
Block: 74520 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1111404 RingCT/type: yes/0
Extra: 01770e470ac4cff424643a98d197f01ca0e291d5380d8f91c9ef672f2171b36a2c02110000022ac71d3ff9000000000000000000

1 output(s) for total of 347.604270427000 dcy

stealth address amount amount idx
00: 8a4761fa3ffd18296fbd915f390b8f061b8cb8c614faacf2ffcf69ce5682327b 347.604270427000 137900 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": 74530, "vin": [ { "gen": { "height": 74520 } } ], "vout": [ { "amount": 347604270427, "target": { "key": "8a4761fa3ffd18296fbd915f390b8f061b8cb8c614faacf2ffcf69ce5682327b" } } ], "extra": [ 1, 119, 14, 71, 10, 196, 207, 244, 36, 100, 58, 152, 209, 151, 240, 28, 160, 226, 145, 213, 56, 13, 143, 145, 201, 239, 103, 47, 33, 113, 179, 106, 44, 2, 17, 0, 0, 2, 42, 199, 29, 63, 249, 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