Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 766f01f85dd403e276492341b3b046619d742bab397b2aaeef55c0d40b30e73f

Tx prefix hash: 4ba25f8422bd27de7494438c745a02012ccbb3600c1c0c84ecf3b9428737b6ff
Tx public key: cef8997e74815d8f6fc80397a2907c1c58fa775f7ad8b5ead3d9a1e6140316ae
Timestamp: 1719169838 Timestamp [UCT]: 2024-06-23 19:10:38 Age [y:d:h:m:s]: 01:136:14:53:45
Block: 1050657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356204 RingCT/type: yes/0
Extra: 01cef8997e74815d8f6fc80397a2907c1c58fa775f7ad8b5ead3d9a1e6140316ae02110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d5431977b2fc9ac25dc8c21f4676017eabadc7ad2e679021bfec29321ec3a13 0.600000000000 1520832 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": 1050667, "vin": [ { "gen": { "height": 1050657 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d5431977b2fc9ac25dc8c21f4676017eabadc7ad2e679021bfec29321ec3a13" } } ], "extra": [ 1, 206, 248, 153, 126, 116, 129, 93, 143, 111, 200, 3, 151, 162, 144, 124, 28, 88, 250, 119, 95, 122, 216, 181, 234, 211, 217, 161, 230, 20, 3, 22, 174, 2, 17, 0, 0, 0, 7, 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