Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 393bc8694965614ddacaa9c4ab8acf10b313df97bd2fa611a375b46c92f38f35

Tx prefix hash: 6917ec53f3eb09c4123490395ddc409f96fd292cc8820dbaeaeeb499d8d884d8
Tx public key: 7e03f072cd589e9f9c8ba01320b75811edd885ea8d6165b882db6715b039af8b
Timestamp: 1718079606 Timestamp [UCT]: 2024-06-11 04:20:06 Age [y:d:h:m:s]: 00:305:15:04:51
Block: 1041646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218406 RingCT/type: yes/0
Extra: 017e03f072cd589e9f9c8ba01320b75811edd885ea8d6165b882db6715b039af8b02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10a3014d5bdc8d376566f6c261d0f085eae8dcad246c5772b1dbe8c4638c251d 0.600000000000 1510371 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": 1041656, "vin": [ { "gen": { "height": 1041646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10a3014d5bdc8d376566f6c261d0f085eae8dcad246c5772b1dbe8c4638c251d" } } ], "extra": [ 1, 126, 3, 240, 114, 205, 88, 158, 159, 156, 139, 160, 19, 32, 183, 88, 17, 237, 216, 133, 234, 141, 97, 101, 184, 130, 219, 103, 21, 176, 57, 175, 139, 2, 17, 0, 0, 0, 4, 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