Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e1a6b89b96afd3ff1afa7c2dbfe79b29ae5919eaafdf5d51d0b04bb44465663

Tx prefix hash: 29662116c77db7beef8f6cea234aee4bffaff1df074cc77d4be62505f43ca88f
Tx public key: d2c0183d747818bc61ed44d1a96a83e9d16b7bb4ac07f752caaa4dedaf7fbff0
Timestamp: 1633208646 Timestamp [UCT]: 2021-10-02 21:04:06 Age [y:d:h:m:s]: 03:094:04:19:32
Block: 345398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 844293 RingCT/type: yes/0
Extra: 01d2c0183d747818bc61ed44d1a96a83e9d16b7bb4ac07f752caaa4dedaf7fbff0021100000001fdc024ec000000000000000000

1 output(s) for total of 44.010213374000 dcy

stealth address amount amount idx
00: 4fde25cb9f017c742f3dc51a4ef7c8a57a186d165c1de4733f39d8f42cbfe8b4 44.010213374000 708556 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": 345408, "vin": [ { "gen": { "height": 345398 } } ], "vout": [ { "amount": 44010213374, "target": { "key": "4fde25cb9f017c742f3dc51a4ef7c8a57a186d165c1de4733f39d8f42cbfe8b4" } } ], "extra": [ 1, 210, 192, 24, 61, 116, 120, 24, 188, 97, 237, 68, 209, 169, 106, 131, 233, 209, 107, 123, 180, 172, 7, 247, 82, 202, 170, 77, 237, 175, 127, 191, 240, 2, 17, 0, 0, 0, 1, 253, 192, 36, 236, 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