Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 446dc77683b2e5a41c683293bec68f9343938ccf1e7daab61eb0a861f2de20ea

Tx prefix hash: 6f70129064284d327270ff90df3ccb504d3c6f3e4c9a82643a7128b8896453ba
Tx public key: e1dc3fba6027c134bfa440396ee519e5ab20b80c7090af987ccbc3a5dff13063
Timestamp: 1591871449 Timestamp [UCT]: 2020-06-11 10:30:49 Age [y:d:h:m:s]: 04:158:15:47:15
Block: 107288 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1047375 RingCT/type: yes/0
Extra: 01e1dc3fba6027c134bfa440396ee519e5ab20b80c7090af987ccbc3a5dff1306302110000001b7db0bdeb000000000000000000

1 output(s) for total of 270.714221110000 dcy

stealth address amount amount idx
00: d50503d4d754c9463031c7f32188f6779f0a8e53a78e1064708248a456c9e0d1 270.714221110000 186908 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": 107298, "vin": [ { "gen": { "height": 107288 } } ], "vout": [ { "amount": 270714221110, "target": { "key": "d50503d4d754c9463031c7f32188f6779f0a8e53a78e1064708248a456c9e0d1" } } ], "extra": [ 1, 225, 220, 63, 186, 96, 39, 193, 52, 191, 164, 64, 57, 110, 229, 25, 229, 171, 32, 184, 12, 112, 144, 175, 152, 124, 203, 195, 165, 223, 241, 48, 99, 2, 17, 0, 0, 0, 27, 125, 176, 189, 235, 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