Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 373933452d26ab70278c07c75c4841ebe3407dfda9cb0117be80c5c57f989617

Tx prefix hash: 9e9b62bc10977b6d5ef4e2fb32c56f737cb31db9959740ee5194a4fd79640bb9
Tx public key: 0bc243ee77bb5a426b49f3005f26d62df17fd8fa1f78ba4251bf4b3f3d77e802
Timestamp: 1719356446 Timestamp [UCT]: 2024-06-25 23:00:46 Age [y:d:h:m:s]: 00:288:09:28:05
Block: 1052213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206082 RingCT/type: yes/0
Extra: 010bc243ee77bb5a426b49f3005f26d62df17fd8fa1f78ba4251bf4b3f3d77e80202110000000d0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b10bfc4d86fe6407e0c89519f2885fd82d123067ed6161855d274b77eae29972 0.600000000000 1522536 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": 1052223, "vin": [ { "gen": { "height": 1052213 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b10bfc4d86fe6407e0c89519f2885fd82d123067ed6161855d274b77eae29972" } } ], "extra": [ 1, 11, 194, 67, 238, 119, 187, 90, 66, 107, 73, 243, 0, 95, 38, 214, 45, 241, 127, 216, 250, 31, 120, 186, 66, 81, 191, 75, 63, 61, 119, 232, 2, 2, 17, 0, 0, 0, 13, 0, 17, 5, 91, 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