Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cdc4b4d3f79d89204385648e7c20a8d6e86017237d99a17ef81f4e0838b619ce

Tx prefix hash: 0c02afe3b7bbc9277c0ff97dbfceba2ce85d3fa8a2c451e98295c4ab125fd8b9
Tx public key: 6bf78a9058764db96ad23caa2442b0e637df77bb39814a57eefe25816ffec8cd
Timestamp: 1729127801 Timestamp [UCT]: 2024-10-17 01:16:41 Age [y:d:h:m:s]: 00:198:12:27:44
Block: 1133233 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141670 RingCT/type: yes/0
Extra: 016bf78a9058764db96ad23caa2442b0e637df77bb39814a57eefe25816ffec8cd02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e918eb5ce9ddde64e35a9e87732770ca6e0b5fd79c3cd59cbf1e758d5cb4e236 0.600000000000 1616312 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": 1133243, "vin": [ { "gen": { "height": 1133233 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e918eb5ce9ddde64e35a9e87732770ca6e0b5fd79c3cd59cbf1e758d5cb4e236" } } ], "extra": [ 1, 107, 247, 138, 144, 88, 118, 77, 185, 106, 210, 60, 170, 36, 66, 176, 230, 55, 223, 119, 187, 57, 129, 74, 87, 238, 254, 37, 129, 111, 254, 200, 205, 2, 17, 0, 0, 0, 2, 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