Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 744559743cdea8257f42c882d63f4cff46402fd3d3b36bc8373cb148100e3839

Tx prefix hash: ae8147cfa0dcb08f13ecfb544c12b9bae5420eb2559483d2c3b3c2a3511c6b37
Tx public key: 9911b11d02359622e3575d815d76f01e3a8b01f4ab0db3ed39249d791be59450
Timestamp: 1728320130 Timestamp [UCT]: 2024-10-07 16:55:30 Age [y:d:h:m:s]: 00:121:07:57:00
Block: 1126531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86475 RingCT/type: yes/0
Extra: 019911b11d02359622e3575d815d76f01e3a8b01f4ab0db3ed39249d791be59450021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ca8cbe67f780243612dc5ab768a8f3c49b9d050e6499eea7cccac41a4f681f0 0.600000000000 1609326 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": 1126541, "vin": [ { "gen": { "height": 1126531 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ca8cbe67f780243612dc5ab768a8f3c49b9d050e6499eea7cccac41a4f681f0" } } ], "extra": [ 1, 153, 17, 177, 29, 2, 53, 150, 34, 227, 87, 93, 129, 93, 118, 240, 30, 58, 139, 1, 244, 171, 13, 179, 237, 57, 36, 157, 121, 27, 229, 148, 80, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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