Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70ed1762ededf328cc55c0f456499c87b43b70af0f8c1203e782eecef63d9cd4

Tx prefix hash: 340d3e79dcf28e9cae88a9d2733dc38cd74c6e911aedfa6ce905893c1adfc8a9
Tx public key: 58bb5a70e86ea82ff05c2e7c1054938e99d275cff1befacfb1711f86b7ef3c36
Timestamp: 1738426669 Timestamp [UCT]: 2025-02-01 16:17:49 Age [y:d:h:m:s]: 00:290:10:38:14
Block: 1209887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205350 RingCT/type: yes/0
Extra: 0158bb5a70e86ea82ff05c2e7c1054938e99d275cff1befacfb1711f86b7ef3c3602110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03d353116eb544939a38ac3baf23b1f6dd0a932782eca0815ca28d0755914d0e 0.600000000000 1696634 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": 1209897, "vin": [ { "gen": { "height": 1209887 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03d353116eb544939a38ac3baf23b1f6dd0a932782eca0815ca28d0755914d0e" } } ], "extra": [ 1, 88, 187, 90, 112, 232, 110, 168, 47, 240, 92, 46, 124, 16, 84, 147, 142, 153, 210, 117, 207, 241, 190, 250, 207, 177, 113, 31, 134, 183, 239, 60, 54, 2, 17, 0, 0, 0, 10, 31, 10, 83, 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