Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 555ddf6c0b613eaae4aa32bad0ea83da8862d49ca2b563e180766dfcc13a6e28

Tx prefix hash: b9f1df927f7ee2c61932109215b4958fb6e71a7a3f11508927f9af93e564b8a5
Tx public key: ab9028509398240ca00f92c48a02bfae474e52745c08f5d51bced8dbb3f1a174
Timestamp: 1697122334 Timestamp [UCT]: 2023-10-12 14:52:14 Age [y:d:h:m:s]: 01:215:15:37:29
Block: 868107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 415176 RingCT/type: yes/0
Extra: 01ab9028509398240ca00f92c48a02bfae474e52745c08f5d51bced8dbb3f1a1740211000000124b8f5122000000000000000000

1 output(s) for total of 0.815832817000 dcy

stealth address amount amount idx
00: 7a6f8270b10a4198b49bde832f90da957c4d686ea9405279e37dc9601819754e 0.815832817000 1322872 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": 868117, "vin": [ { "gen": { "height": 868107 } } ], "vout": [ { "amount": 815832817, "target": { "key": "7a6f8270b10a4198b49bde832f90da957c4d686ea9405279e37dc9601819754e" } } ], "extra": [ 1, 171, 144, 40, 80, 147, 152, 36, 12, 160, 15, 146, 196, 138, 2, 191, 174, 71, 78, 82, 116, 92, 8, 245, 213, 27, 206, 216, 219, 179, 241, 161, 116, 2, 17, 0, 0, 0, 18, 75, 143, 81, 34, 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