Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: adc5781743c2b055b697ae657bd9f3e541535e035206d0b79a260bcd2fd86071

Tx prefix hash: 24278a921bcc8e82127cd597cee9d1ab1e1e44570625c359f7aaaac8804fb7ab
Tx public key: a92e38d7e316941b043c104e67d6db6933f6e9e49442194c73a6b5691320850b
Timestamp: 1715646241 Timestamp [UCT]: 2024-05-14 00:24:01 Age [y:d:h:m:s]: 00:338:08:38:48
Block: 1021452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241873 RingCT/type: yes/0
Extra: 01a92e38d7e316941b043c104e67d6db6933f6e9e49442194c73a6b5691320850b02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a13ba9cee14b001fb5cadd9e13b8610a47e23b2ab04a5948f4431f9d3b9ecfd 0.600000000000 1485777 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": 1021462, "vin": [ { "gen": { "height": 1021452 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a13ba9cee14b001fb5cadd9e13b8610a47e23b2ab04a5948f4431f9d3b9ecfd" } } ], "extra": [ 1, 169, 46, 56, 215, 227, 22, 148, 27, 4, 60, 16, 78, 103, 214, 219, 105, 51, 246, 233, 228, 148, 66, 25, 76, 115, 166, 181, 105, 19, 32, 133, 11, 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