Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73e0be44f11f98d2014930b37ba3b037db49fe647d32dd9799b7e938fb997dc5

Tx prefix hash: 3a4e80ac511646e020cb91f0b8ade97f06a592ea323484d5f215741ebd6bb0e0
Tx public key: 338c11f18dd480dce5a810af7211ef82fe41fe146b290340411f9f3d72d60a74
Timestamp: 1643338900 Timestamp [UCT]: 2022-01-28 03:01:40 Age [y:d:h:m:s]: 02:308:01:04:13
Block: 426775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 738676 RingCT/type: yes/0
Extra: 01338c11f18dd480dce5a810af7211ef82fe41fe146b290340411f9f3d72d60a74021100000026c9067537000000000000000000

1 output(s) for total of 23.654707112000 dcy

stealth address amount amount idx
00: 48ea9e22617482c5557f5645c82f31d5cfdab5a8d10c5edc731fb9d2ebf68f2e 23.654707112000 835709 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": 426785, "vin": [ { "gen": { "height": 426775 } } ], "vout": [ { "amount": 23654707112, "target": { "key": "48ea9e22617482c5557f5645c82f31d5cfdab5a8d10c5edc731fb9d2ebf68f2e" } } ], "extra": [ 1, 51, 140, 17, 241, 141, 212, 128, 220, 229, 168, 16, 175, 114, 17, 239, 130, 254, 65, 254, 20, 107, 41, 3, 64, 65, 31, 159, 61, 114, 214, 10, 116, 2, 17, 0, 0, 0, 38, 201, 6, 117, 55, 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