Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0323c5a581486f50cfed9e0931b67d6b76902aab43a171cd217eae4f26c834f2

Tx prefix hash: 75920ebd4df31b14b293501d9be33b684eb5fd67cb34d4135a8b6bcdbd7d7a3a
Tx public key: 27bfd2871eef1f50e6c0525a90f7c3a76b2369b72454679f1de25292fbf1402f
Timestamp: 1578687009 Timestamp [UCT]: 2020-01-10 20:10:09 Age [y:d:h:m:s]: 05:053:09:01:10
Block: 42943 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1188065 RingCT/type: yes/0
Extra: 0127bfd2871eef1f50e6c0525a90f7c3a76b2369b72454679f1de25292fbf1402f021100000001d81c26c0000000000000000000

1 output(s) for total of 442.295843248000 dcy

stealth address amount amount idx
00: 01fad450220b42dc806725efdc99accc642806d6bb99cb63b2650c839ff99d5c 442.295843248000 77511 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": 42953, "vin": [ { "gen": { "height": 42943 } } ], "vout": [ { "amount": 442295843248, "target": { "key": "01fad450220b42dc806725efdc99accc642806d6bb99cb63b2650c839ff99d5c" } } ], "extra": [ 1, 39, 191, 210, 135, 30, 239, 31, 80, 230, 192, 82, 90, 144, 247, 195, 167, 107, 35, 105, 183, 36, 84, 103, 159, 29, 226, 82, 146, 251, 241, 64, 47, 2, 17, 0, 0, 0, 1, 216, 28, 38, 192, 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