Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75cb73176fd9bd51456ad60df88a2c47197d05f18dd4af03261ec864efbc6ada

Tx prefix hash: 7e1d97c43fad8f8e432d3ca08743719e4b5d77dcc0e0a8e2286e9d0a056e2abc
Tx public key: fe776e8de33f46c7329e7d46bc39999736f4ae51043cf8afbe5d5f301af23599
Timestamp: 1707591820 Timestamp [UCT]: 2024-02-10 19:03:40 Age [y:d:h:m:s]: 01:118:09:35:00
Block: 954676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345717 RingCT/type: yes/0
Extra: 01fe776e8de33f46c7329e7d46bc39999736f4ae51043cf8afbe5d5f301af235990211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 107e26d517018988f5487741120b0f9157028d6c5b76f1e3ba47860f0ecfb7d3 0.600000000000 1413956 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": 954686, "vin": [ { "gen": { "height": 954676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "107e26d517018988f5487741120b0f9157028d6c5b76f1e3ba47860f0ecfb7d3" } } ], "extra": [ 1, 254, 119, 110, 141, 227, 63, 70, 199, 50, 158, 125, 70, 188, 57, 153, 151, 54, 244, 174, 81, 4, 60, 248, 175, 190, 93, 95, 48, 26, 242, 53, 153, 2, 17, 0, 0, 0, 9, 0, 17, 5, 91, 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