Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a835e204b3d84e2b5045e0aca899f89c2fe6579ff8ca2691d04ba0eddce38c32

Tx prefix hash: 8e8ed79fba17ad559f4de5e803657e64c5aa744e1fec1b9ec3c8304032d0fe6e
Tx public key: 23769165affa0b431599676f437e450551a0ba16299b9f0acefdf59eb7f48c0d
Timestamp: 1709437805 Timestamp [UCT]: 2024-03-03 03:50:05 Age [y:d:h:m:s]: 01:051:04:18:57
Block: 969993 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297592 RingCT/type: yes/0
Extra: 0123769165affa0b431599676f437e450551a0ba16299b9f0acefdf59eb7f48c0d02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3b3b32c4cde319fc339c9919dc4f5896b7b77d440b5a2b2f8572c65745366d3 0.600000000000 1429842 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": 970003, "vin": [ { "gen": { "height": 969993 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3b3b32c4cde319fc339c9919dc4f5896b7b77d440b5a2b2f8572c65745366d3" } } ], "extra": [ 1, 35, 118, 145, 101, 175, 250, 11, 67, 21, 153, 103, 111, 67, 126, 69, 5, 81, 160, 186, 22, 41, 155, 159, 10, 206, 253, 245, 158, 183, 244, 140, 13, 2, 17, 0, 0, 0, 3, 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