Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc861693106386974d00fe8302f0f367b5758c03456b11b309e4d2342751935e

Tx prefix hash: e732ae6583287c4cf576a3e8cb4f5ef8f9fc3e204ed5a86de3f232347c33e3f7
Tx public key: d136bab6f512e18f02be19a6aca25e47ff7a3cb7bb024bf691110f8e65a95d1c
Timestamp: 1728773779 Timestamp [UCT]: 2024-10-12 22:56:19 Age [y:d:h:m:s]: 00:172:20:14:22
Block: 1130296 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123302 RingCT/type: yes/0
Extra: 01d136bab6f512e18f02be19a6aca25e47ff7a3cb7bb024bf691110f8e65a95d1c02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e4cb501392005fb4a6895873142cc34dfe19cf8a08e0418ac559a5c3b541490 0.600000000000 1613171 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": 1130306, "vin": [ { "gen": { "height": 1130296 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e4cb501392005fb4a6895873142cc34dfe19cf8a08e0418ac559a5c3b541490" } } ], "extra": [ 1, 209, 54, 186, 182, 245, 18, 225, 143, 2, 190, 25, 166, 172, 162, 94, 71, 255, 122, 60, 183, 187, 2, 75, 246, 145, 17, 15, 142, 101, 169, 93, 28, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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