Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed5cab11ebd0315f5c45884d7b1b2fc5efc3afbeec601f6fb4150d45c28289a1

Tx prefix hash: f850984311e5727912f6804f8109bc9b33f13a428186d8236b1c004c7aecd193
Tx public key: 9aea2fb9ef2d84f5b533b220700f020f7f20bc566bdd0c27e87b1af271781282
Timestamp: 1723065306 Timestamp [UCT]: 2024-08-07 21:15:06 Age [y:d:h:m:s]: 00:240:00:26:07
Block: 1082962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171428 RingCT/type: yes/0
Extra: 019aea2fb9ef2d84f5b533b220700f020f7f20bc566bdd0c27e87b1af27178128202110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 705e078f722b4ff8ba60b9771e67f73a28dec328d64bf36d43e71535e332f1b9 0.600000000000 1556797 of 15

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": 1082972, "vin": [ { "gen": { "height": 1082962 } } ], "vout": [ { "amount": 600000000, "target": { "key": "705e078f722b4ff8ba60b9771e67f73a28dec328d64bf36d43e71535e332f1b9" } } ], "extra": [ 1, 154, 234, 47, 185, 239, 45, 132, 245, 181, 51, 178, 32, 112, 15, 2, 15, 127, 32, 188, 86, 107, 221, 12, 39, 232, 123, 26, 242, 113, 120, 18, 130, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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