Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 668463335c96a4114b8ad9c01e7df1c5e30586e7b3f1503fb654d59f7134166f

Tx prefix hash: 229949cc7e4e1ddf72c06df7d9603243a7cba7652752f267cf916a14e45360c9
Tx public key: bee5c074e4bac88504fb2a62ce00db5358534bc0c45672ef80b1b69e9cafc7aa
Timestamp: 1714225078 Timestamp [UCT]: 2024-04-27 13:37:58 Age [y:d:h:m:s]: 00:200:19:48:51
Block: 1009669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143764 RingCT/type: yes/0
Extra: 01bee5c074e4bac88504fb2a62ce00db5358534bc0c45672ef80b1b69e9cafc7aa02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b8f1564216347d82430652b208b7128a6ec7e35ba947f65fa8c710196ea9858 0.600000000000 1471409 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": 1009679, "vin": [ { "gen": { "height": 1009669 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b8f1564216347d82430652b208b7128a6ec7e35ba947f65fa8c710196ea9858" } } ], "extra": [ 1, 190, 229, 192, 116, 228, 186, 200, 133, 4, 251, 42, 98, 206, 0, 219, 83, 88, 83, 75, 192, 196, 86, 114, 239, 128, 177, 182, 158, 156, 175, 199, 170, 2, 17, 0, 0, 0, 1, 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