Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e259f7b522d2f24dcf8fbf2a9c44e3beacf81db2125431e376ee848e368176ef

Tx prefix hash: 193f17068fe7fc37480b162daea9cf11482b2352fdff247a049e0aa22f3be284
Tx public key: e376d16a7cae13cbb8216db29ff4622bde7c0f59665f3366b5caf1271d47185b
Timestamp: 1706574728 Timestamp [UCT]: 2024-01-30 00:32:08 Age [y:d:h:m:s]: 01:070:08:56:38
Block: 946230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311381 RingCT/type: yes/0
Extra: 01e376d16a7cae13cbb8216db29ff4622bde7c0f59665f3366b5caf1271d47185b02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1932464a4d11a0edd6c15acf6d5f837fc1003fd8c7d597b409a3e8ce5dc32ab 0.600000000000 1404562 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": 946240, "vin": [ { "gen": { "height": 946230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1932464a4d11a0edd6c15acf6d5f837fc1003fd8c7d597b409a3e8ce5dc32ab" } } ], "extra": [ 1, 227, 118, 209, 106, 124, 174, 19, 203, 184, 33, 109, 178, 159, 244, 98, 43, 222, 124, 15, 89, 102, 95, 51, 102, 181, 202, 241, 39, 29, 71, 24, 91, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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