Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d99218176e694b51f3a62172b478527d92c863e00b74a479a51f01ffb7177df

Tx prefix hash: 9a8e0cdab9884333a97e3f2aa506928331627798d57f16e9e83e4ba2471d79ed
Tx public key: ece534c69c68f0d009217f5037bf728c8343ea1ab1dba30b6d3d36e71c7aa3e4
Timestamp: 1719899334 Timestamp [UCT]: 2024-07-02 05:48:54 Age [y:d:h:m:s]: 00:295:03:32:31
Block: 1056723 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210890 RingCT/type: yes/0
Extra: 01ece534c69c68f0d009217f5037bf728c8343ea1ab1dba30b6d3d36e71c7aa3e40211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f70d8cdd312433f11fdc503176e941e312ea1b73ac9ba3e1d11a088ae002be1 0.600000000000 1527144 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": 1056733, "vin": [ { "gen": { "height": 1056723 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f70d8cdd312433f11fdc503176e941e312ea1b73ac9ba3e1d11a088ae002be1" } } ], "extra": [ 1, 236, 229, 52, 198, 156, 104, 240, 208, 9, 33, 127, 80, 55, 191, 114, 140, 131, 67, 234, 26, 177, 219, 163, 11, 109, 61, 54, 231, 28, 122, 163, 228, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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