Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1eb52614ab3a33b24bc180bd2d43e028ab8980641106c545d6aec9aacd99830c

Tx prefix hash: 1ba6b306c73f03bcfae79ce9c359ab6f60a9d97a20d59fbe45dddb1dc947c0f7
Tx public key: ea884ff882a6a58a374929222832c3e10fa067f449066a8b2416b5a0a57d3195
Timestamp: 1717578769 Timestamp [UCT]: 2024-06-05 09:12:49 Age [y:d:h:m:s]: 00:362:15:03:51
Block: 1037484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259200 RingCT/type: yes/0
Extra: 01ea884ff882a6a58a374929222832c3e10fa067f449066a8b2416b5a0a57d319502110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 759916e767af3bf82d1eb274c84bb36440aa28cb6561edc66e2ab89422b34f39 0.600000000000 1506029 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": 1037494, "vin": [ { "gen": { "height": 1037484 } } ], "vout": [ { "amount": 600000000, "target": { "key": "759916e767af3bf82d1eb274c84bb36440aa28cb6561edc66e2ab89422b34f39" } } ], "extra": [ 1, 234, 136, 79, 248, 130, 166, 165, 138, 55, 73, 41, 34, 40, 50, 195, 225, 15, 160, 103, 244, 73, 6, 106, 139, 36, 22, 181, 160, 165, 125, 49, 149, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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