Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f1a499e72b61dddb9dd0c506d7be956b728a3744112ce8bbb926dbae374fa0f

Tx prefix hash: d4d2cffab6947d52c34a63e04fbe1eda846a11ca92f22565fe82ab8156d8e36e
Tx public key: d5cb8c833b488105c9dcc1f7b213be94845a1b0710b4048fe6fb62fa647ef281
Timestamp: 1718568206 Timestamp [UCT]: 2024-06-16 20:03:26 Age [y:d:h:m:s]: 00:276:00:39:20
Block: 1045698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197254 RingCT/type: yes/0
Extra: 01d5cb8c833b488105c9dcc1f7b213be94845a1b0710b4048fe6fb62fa647ef28102110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc4540b4f233426cbad263e626b66a763a5298b8a7be8835374588591f8ecb16 0.600000000000 1515337 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": 1045708, "vin": [ { "gen": { "height": 1045698 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc4540b4f233426cbad263e626b66a763a5298b8a7be8835374588591f8ecb16" } } ], "extra": [ 1, 213, 203, 140, 131, 59, 72, 129, 5, 201, 220, 193, 247, 178, 19, 190, 148, 132, 90, 27, 7, 16, 180, 4, 143, 230, 251, 98, 250, 100, 126, 242, 129, 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