Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b981cf6d3054f4b50f14c656f9497bf3149c0b47602097803be68f6a78cbdf46

Tx prefix hash: 6e7283490cd6de0be778ebaa533b95329f7d80e2701a0716e22c121510d98e1a
Tx public key: 41ead6d50bcaa3e5ccac6ef094e24886e657ecd690e9b0319fb86dc5b2eaed28
Timestamp: 1580491053 Timestamp [UCT]: 2020-01-31 17:17:33 Age [y:d:h:m:s]: 04:292:16:23:29
Block: 56192 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1100115 RingCT/type: yes/0
Extra: 0141ead6d50bcaa3e5ccac6ef094e24886e657ecd690e9b0319fb86dc5b2eaed28021100000002dcee4b4d000000000000000000

1 output(s) for total of 399.772946842000 dcy

stealth address amount amount idx
00: de1446ad7eca3cf533f4dcd8d54b2e0b9240015ef9a28eb264433a5fe55c8aea 399.772946842000 103576 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": 56202, "vin": [ { "gen": { "height": 56192 } } ], "vout": [ { "amount": 399772946842, "target": { "key": "de1446ad7eca3cf533f4dcd8d54b2e0b9240015ef9a28eb264433a5fe55c8aea" } } ], "extra": [ 1, 65, 234, 214, 213, 11, 202, 163, 229, 204, 172, 110, 240, 148, 226, 72, 134, 230, 87, 236, 214, 144, 233, 176, 49, 159, 184, 109, 197, 178, 234, 237, 40, 2, 17, 0, 0, 0, 2, 220, 238, 75, 77, 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