Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c03cb87806509282804be960dfa5a775f0ee966721583cedf51feae38bdb3f15

Tx prefix hash: 86706e7dac5f612db46f1323ae1fff625c257205050da615e7164cf8dc3c455d
Tx public key: a36a33ef9259743988f40e9c031f3ce6fdc8c2a5321f6b20ecc5cee66ed27530
Timestamp: 1705651147 Timestamp [UCT]: 2024-01-19 07:59:07 Age [y:d:h:m:s]: 01:148:22:01:20
Block: 938573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367478 RingCT/type: yes/0
Extra: 01a36a33ef9259743988f40e9c031f3ce6fdc8c2a5321f6b20ecc5cee66ed2753002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8165b4a5c2a72d080910b2a43ec3cf4f2e55496fed07b2b19d78873aa57da72 0.600000000000 1396643 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": 938583, "vin": [ { "gen": { "height": 938573 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8165b4a5c2a72d080910b2a43ec3cf4f2e55496fed07b2b19d78873aa57da72" } } ], "extra": [ 1, 163, 106, 51, 239, 146, 89, 116, 57, 136, 244, 14, 156, 3, 31, 60, 230, 253, 200, 194, 165, 50, 31, 107, 32, 236, 197, 206, 230, 110, 210, 117, 48, 2, 17, 0, 0, 0, 1, 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